NOTICE: This forum is mostly an archive, though new posts are allowed. Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by nah1982, December 18, 2020, 11:37:57 PM
Quote from: Jeremy Collake on December 19, 2020, 09:49:06 AMEnabling the CPU affinity rules to properly function after changes to the system CPU core count is under consideration (issue #777).Allowing 0-* type rules is an option.I don't have any ETA to give you, but it is on the radar. I'll post here when progress occurs.Thanks for the feedback!
Quote from: Jeremy Collake on December 21, 2020, 09:43:02 AMI went ahead and made this change (strip unavailable CPUs from CPU affinities prior to applying them) to v220.127.116.11 beta.If you try it, let me know how it treats you. I believe it is the simplest and most effective way to handle this scenario. It is effectively the same as n-*.
Quote..it still is attempting to apply the rules constantly, like it's detecting they're still not set to the original rule vs. taking the rule and only applying it up to the maximum available.
Quote from: Jeremy Collake on December 27, 2020, 01:08:35 PMGive 18.104.22.168 beta a spin. Let me know how it goes!