Started by Jeremy Collake, June 04, 2010, 02:22:47 AM
Quote"Bitsum Technologies has recently improved the default ProBalance parameters (settings). Would you like to adopt these new settings? Other settings are not affected. It is recommended you simply click YES unless you have customized the ProBalance parameters."
Quote from: jeremy.collake on June 13, 2010, 11:22:53 PMI would like to ask about the difference in v3.99 behavior. Are there any different/new log entries now? I changed a few default settings, and many other things, but am more importantly curious if Emergency Stall Recovery is kicking in or not.Some disk defragmentors are excluded from ProBalance restraint because they can be sensitive to priority adjustments. I always play it safe ;o.
Quote from: jeremy.collake on June 13, 2010, 11:50:38 PMNew text is: Quote"Bitsum Technologies has recently improved the default ProBalance parameters (settings). Would you like to adopt these new settings? Other settings are not affected. It is recommended you simply click YES unless you have customized the ProBalance parameters."And, yes, maybe it would be better just to do it, and then tell people I did it.. However, I'd then get some complaints from the minority who do adjust those settings.
Quote from: LordPE MajorOperatingSystemVersion: 0x0005 MinorOperatingSystemVersion: 0x0001 -> 5.01
Quote from: watermelon on September 19, 2010, 07:23:54 AMA couple of questions, like always: Is there an exact list of what features are not enabled in the unpaid version? I didn't activate the beta yet and aside from the one notification on startup I couldn't find another hint what actually works and what not.
QuoteWanting to give the ESR a try, I disabled ProBalance for a moment and fired up CPUEater while having another process performing some I/O, bringing responsiveness to a minimum with even the mouse barely moving. Waiting for 2 minutes without the ESR taking any action, is that because my version is not activated or is the ESR only triggered later (too late imo then)?
QuoteFinally I can disable logging, thank you.
QuoteHow far along are you with the features of the Watchdog? I have to ask because the only action that I could make use of is basiscally always going to result in the process being terminated. I'd much prefer to a) lower the priority of a process and b) trim the memory as can be done manually already and with ProBalance.
QuoteI remember you wanting to rename the 'virtual memory' references, they are still the same it seems. Trimming virtual memory will actually trim the working set which is physical memory. If you are intending to actullay trim virtual memory it isn't working for me.
QuoteAlso, if I may ask, what information is being transmitted when activating?
QuoteThank you again, PE4 will be an even more powerful tool than it already was before.
QuoteAfter some hours of running the new version, the ProcessGovernor.exe consumes twice as much virtual and physical memory than 3.89 beta did. On startup it has 4MB working set 3MB virtual memory versus the old version below 3MB working set and 1.4MB virtual memory. The memory usage increases to 9MB after a while.. it's never been that high before.