Process Lasso: About the new ProBalance ‘Frequency of Action’

[Batu69]

 

TODO – Do not publish until algorithm finalized.

 

I always hated using the term ‘Restraint’ for ProBalance ‘Actions’, as they may not yield any performance difference at all unless there is contention for the CPU. Usually it takes a very slight bit of CPU cycles to restore responsiveness, thus I do not want to make it sound like ProBalance’s temporary, marginal adjustments are heavy-handed when they are not.

 

So for those wondering, that is why we are calling them ‘Actions’ now. Besides, given new features of ProBalance, they could do all kinds of things.

This new metric was first represented in CPUBalance ALPHA (about to go BETA), and will be present in Process Lasso v9 (currently in ALPHA).

 

The math has some additional variables for better showmanship, but basically comes down to: total_time_of_process_run DIVIDED BY times_acted_on. The duration of action can play a factor too, I don’t want to fully define it publicly because it is still being tweaked.

 

YES, this will be in Process Lasso v9, but not Process Lasso v8. Regarding licensing, since it is time based, the major version doesn’t matter so much – thus it is all marketing and taking the product to the next level (which we have done!).

 

Article source