Windows 2000 Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Sunday, 16 May 2010

Yet another warning about these 'booster' utilities that set the foreground process priority class to High

Posted on 08:35 by Unknown
I wanted to take a minute to issue yet another warning about these gimmicky process optimization utilities that do nothing more than set the foreground process priority class to High. You may say, "well, that seems reasonable", but the truth is that it is NOT effective and can be VERY dangerous. That is why foreground boosting is disabled in Process Lasso by default.

The Windows Scheduler already gives foreground threads higher precedence by giving them longer time slices. You do not want to give them a higher priority because this can lead to starvation of other CRITICAL system processes. Not only does theory say additional foreground boosting is ineffective, but so does empirical evidence. Hundreds of tests on our systems have shown foreground boosting to be ineffective and dangerous. Not only does it not work to improve responsiveness or speed of the foreground process, it can result in priority inversions and maybe even deadlocks in an unlikely worst case scenario. It would definitely result in deadlocks if Windows didn't have built in deadlock avoidance.

This is why Process Lasso's ProBalance algorithm lowers select background process priorities instead of foreground boosting. Furthermore, even a ProBalance like mechanism must be carefully tuned and tested. We have spent years refining our algorithm, and use it every day ourselves -- unlike these slimy developers who just want to sell you something, whether it works or not.

Now, can foreground boosting sometimes boost performance of some applications in some scenarios? Sure, but in such cases it is better to change their default/persistent priority class instead of boosting each process that goes to the foreground to the High priority class. That is not what you want to do, trust me.

I am busy programming this morning and don't have the time to go into detail again, but please do not use these utilities! They are created by developers who want to do something *really* simple (can be done in a few lines of code) and claim it boosts your PC performance. Please, stay away!

More written on this here: About ProBalance and the Windows CPU Scheduler
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • WARNING: Cracks for Process Lasso may modify HOSTS file
    WARNING:  Cracks for Process Lasso have been seen to modify your system HOSTS file so that you can no longer access  bitsum.com  and/or  bit...
  • Process Lasso and WDFME
    Since Process Lasso can be complex for the layman, something we are working on, I wanted to list a set of steps to address the commonly abu...
  • Tightening the Governor
    Most users of Process Lasso are familiar with its core engine, ProcessGovernor.exe. It is the silent background process that applies all pro...
  • Anti-virus software - the #1 cause of PC performance troubles
    Many users realize their anti-virus software consumes massive amounts of system resources, and hope that Process Lasso will somehow keep it ...
  • The many instances of Chrome
    As many readers of this blog may know, Google Chrome is different from other Windows web browsers. It isolates each of its tabs into an indi...
  • Oh the frustration with this corporate crapware!!
    I now get uninstall feedback, as I solicit it (for better or worse). Once read, I can never go back, lol. Fortunately, most of it is actuall...
  • Process Lasso v5.0.0.48
    Changes: [.48]Change.GUI: Do not show 'Activate Now' menu item after activation [.48]Change.GUI: Adjusted logging thread CPU and I/O...
  • ParkControl updated to v1.0.0.0
    This nifty utility, included in Process Lasso v6, lets you enable or disable CPU core parking in REAL TIME , no reboot required. It also let...
  • Next update, Options menu gets some changes
    I decided to make the Options menu a little more consistent and move the ProBalnce configuration down with the rest of the rules configurati...
  • If you are seeing random crashes of the GUI or core engine ...
    Many users of Process Lasso have experimented with various system 'optimization' utilities. Many of these make permanent changes to ...

Blog Archive

  • ►  2013 (1)
    • ►  March (1)
  • ►  2012 (6)
    • ►  September (1)
    • ►  July (1)
    • ►  June (2)
    • ►  January (2)
  • ►  2011 (166)
    • ►  December (3)
    • ►  November (2)
    • ►  October (2)
    • ►  September (6)
    • ►  August (12)
    • ►  July (14)
    • ►  June (17)
    • ►  May (19)
    • ►  April (13)
    • ►  March (27)
    • ►  February (31)
    • ►  January (20)
  • ▼  2010 (203)
    • ►  December (23)
    • ►  November (34)
    • ►  October (38)
    • ►  September (17)
    • ►  August (19)
    • ►  July (19)
    • ►  June (11)
    • ▼  May (16)
      • Memorial Day weekend releases
      • A new review of Process Lasso
      • Optimizing process icon memory use & New core feat...
      • New CPU Eater goes final
      • Process Lasso v3.85.1 beta released
      • Process Lasso v3.84.4 final
      • v3.85 beta series starts
      • New first time minimize to systray greeting (in fu...
      • The v4 release plan (lots of v3 updates)
      • CPUEater v4 early preview
      • Giveaway of the Day Promotion - Great success!
      • The difficulties of being an independent developer...
      • Yet another warning about these 'booster' utilitie...
      • Quick refresh of v3.84.2 - updated French and smal...
      • Example of real world software error condition tha...
      • v3.84.2 - another very minor update
    • ►  April (8)
    • ►  March (6)
    • ►  February (6)
    • ►  January (6)
  • ►  2009 (43)
    • ►  December (6)
    • ►  November (1)
    • ►  October (10)
    • ►  September (3)
    • ►  August (1)
    • ►  July (9)
    • ►  June (2)
    • ►  May (3)
    • ►  April (4)
    • ►  March (4)
Powered by Blogger.

About Me

Unknown
View my complete profile