ProBalance effect inherited by child processes?

Started by Joe0Bloggs, January 09, 2026, 09:06:58 AM

Previous topic - Next topic

Joe0Bloggs

There are now three things ProBalance can change:
1. Process Priority
2. Process "Efficiency" flag
3. Process CPU affinity

From trial and error, it seems that 1 and 2 correctly apply temporarily and only to the process(es) in question themselves, whereas (3) can become "sticky" and even stick to processes created by the parent process while being restrained?

I suppose this is not news.  But just want to confirm.  And if true, (that only (3) is like that), the option to change affinity via ProBalance should come with a warning as such.  :)

Jeremy Collake

That's a good observation! I can confirm that if you were to use the CPU affinity option of ProBalance (few people do) it could propagate to child processes launched while the parent process is restrained. I've created a ticket to consider how to best address this and we will certainly at least add a warning about it.

Thanks for the heads up!
Software Engineer. Bitsum LLC.


Jeremy Collake

My apologies that this wasn't addressed sooner. It slipped through the cracks.

In the v19.0 final planned for this week, we've added a tooltip to warn about this behavior.

Beginning in the next beta series (also this week), we'll implement the proper fix to ensure that child processes launched during a ProBalance restraint don't inherit the effects of the restrained state. I'll reply again when this is in.
Software Engineer. Bitsum LLC.

Jeremy Collake

This is in the Process Lasso 19.1.0.5 beta. Turn on Options > CPU > ProBalance > Restore CPU Affinity of Child Processes. It's also in the Advanced ProBalance Options dialog, under "Change affinity during restraint", which must be on for it to apply.

With it on, a process started while ProBalance had changed its parent's CPU affinity gets the parent's original affinity instead of keeping the restrained one. An affinity rule you've set for that process still takes precedence.

It's off by default because it changes behavior that some users may rely on. We may turn it on by default for new installs later. Please let us know how it works for you.
Software Engineer. Bitsum LLC.

viderbeli

That is an important distinction, especially when dealing with applications that spawn multiple child processes.

Joe0Bloggs

Quote from: Jeremy Collake on November 04, 2026, 06:37:48 PMThis is in the Process Lasso 19.1.0.5 beta. Turn on Options > CPU > ProBalance > Restore CPU Affinity of Child Processes. It's also in the Advanced ProBalance Options dialog, under "Change affinity during restraint", which must be on for it to apply.

With it on, a process started while ProBalance had changed its parent's CPU affinity gets the parent's original affinity instead of keeping the restrained one. An affinity rule you've set for that process still takes precedence.

It's off by default because it changes behavior that some users may rely on. We may turn it on by default for new installs later. Please let us know how it works for you.

Ah!  I'll download the beta to find out then!

Joe0Bloggs

It seems to work as expected.  It's just that the default settings when combined with my option to constrain restrained processes to one processor tends to cause whiplash restricting and the processor switching itself seems to cause slowdowns.

Jeremy Collake

#8
Thanks for testing the beta, and glad the fix works as expected.

Limiting restrained processes to a single CPU is an aggressive setting. Each restraint squeezes the process onto one core, then it spreads back out when the restraint ends, and that back-and-forth can hurt more than it helps. Two things to try: allow more than one core in the restraint affinity, or leave the affinity change off and let the priority and Efficiency restraint do the work. ProBalance's main effect comes from those two anyway.

If you can share your CPU model, which processes are typically restrained, and what you want the affinity restraint to achieve, we can suggest settings that fit.
Software Engineer. Bitsum LLC.