Started by Jeremy Collake, September 02, 2012, 01:29:47 AM
Total Members Voted: 2
QuoteEssentially, in high loads, it will get disabled for a while (when ProBalance is active), then re-enabled
QuoteI want to make cores parked more visible, and the current configuration more visible in the GUI. Also, in the case of an improper termination of the governor, it must be able to restore the original settings, as it does in the case of power profiles.
Quote from: BenYeeHua on September 02, 2012, 02:08:40 AMThat what I worry about, an improper termination of the governor when it had disable core-parking.
Quoteit retrieves the 'right' values and restores them.
QuoteIt also raises the possibility of allowing the inexperienced or uninterested users who don't want or need anything but hands-free automation from PL to just sit back.
Quote from: BenYeeHua on September 02, 2012, 01:10:03 PMSo you just record the CPU usage per-process/overall, and decide that which value is suitable for you
Quoteeven the governor running at high priority can have trouble intervening.
Quote from: bitsum.support on September 02, 2012, 04:47:36 PMbertie, I'm in a bit of a rush, so will respond more later (sorry), but the values you see as defaults are actually determined on a per-machine basis, using algorithms I don't want to publicly disclose . I have done a lot of testing to make sure they are what they should be, and there are reasons why they might appear to be overly sensitive. Yes, I'm being vague, but remember, I have [lame corporate snake oil] competitors
QuoteRemember, Process Lasso has been around like 15 years now (originally named Process Supervisor).
QuoteI want to explain what I can about why certain settings are best, without giving away any secrets ;p. After all, it took me *years* to learn some.