Hello,
I tried Process Lasso today on my 245KF and found something interesting while isolating Skymont performance.
It works, but the single enabled Lion Cove core shows minimal activity only if:
The application doesn't ignore process affinity.
The application has a single process without any child processes. If there are child processes, you'll need to check their CPU utilization to adjust the process affinity, and they might ignore it too.
The process isn't engaged in file I/O. Essentially, any process that writes to files is likely to access the core you've restricted.
Noticed No.3 happening with Rapydmark and Handbrake. The former touched the lone Lion Cove core in the file based subtests and Handbrake was unable to ignore the Lion Cove core as well. y-cruncher straight away ignored process affinity, maybe because it's writing to a validation file?
You can check menu item "
Options > Forced Mode" to deal with processes that ignore (set their own) CPU affinities. That should also handle cases of where the CPU affinity wasn't propagated to the child processes like you expected.
QuoteThe process isn't engaged in file I/O. Essentially, any process that writes to files is likely to access the core you've restricted.
I'm not sure the reasoning on this is valid. I/O shouldn't be bound to a particular CPU core, and definitely not one you've excluded from the affinity. You may have seen something else going on. If you've made larger adjustments, such as CPU affinities to system processes, then those should be evaluated.
Let me know how that goes!