Windows 2000 Support

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

Friday, 20 August 2010

New watchdog option to divide CPU % thresholds by the CPU count (read to clarify)

Posted on 00:44 by Unknown
ictures say a thousand words.

I've added a new GLOBAL Watchdog option to divide *all* CPU thresholds by the number of CPUs on the target system. This lets you set a static value (e.g. 100%) and that value be relative to the total CPU count on the system to which it is applied. Its useful mostly for single thread apps. Consider the case of a single thread consuming every CPU cycle it can get. On a single core system, this is 100%... but on a dual core system, it is 50%, and on a quad core system it is 25%, etc..

This is the new Watchdog config dialog in v3.99.11 alpha, coming within hours:



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

  • Process Lasso v5.0.0.28
    This build continues maintenance, fixing several items and also making a nice improvement to the graph's display. Further, the last sele...
  • 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 ...
  • 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...
  • Optimizing process icon memory use & New core feature coming..
    Two in one post. Yes, here at Bitsum we're going Green by conserving bandwidth ;). Of course, that's just a joke and I fully support...
  • Indonesian language added - That makes 11
    Thanks to the work of Ivan Chin, an Indonesian (Bahasa Melayu) translation will be included in v3.99.36. This will be the first time even he...
  • 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...
  • 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...
  • 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...
  • 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...
  • BETA: Vista startup configuration
    Ok, I've got this fully correct now I think. In some cases in previous builds you could end up with both registry and Task Scheduler sta...

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)
      • A couple backports to v3.84.7
      • Graph tooltips coming (for real)
      • Process Lasso v3.99.17 beta - fixes install error ...
      • v3.99.15 beta - a solid stride forward
      • New version 4 activation system completed
      • Going beta
      • Builds coming fast, v3.99.12 alpha hits
      • New watchdog option to divide CPU % thresholds by ...
      • v3.99.11 beta coming tomorrow
      • Beware of imitators
      • v3.99.10 updated - all builds now the same (activa...
      • Activation codes assigned
      • All users being assigned activation codes
      • v3.99.10 released - but another alpha, not beta
      • Limited time home license sale (5 days)
      • Results of TrialPay experiment
      • Version 4 (v3.99) - Introducing faster load time a...
      • When does the evolution of v4 stop?
      • Activation code confusion
    • ►  July (19)
    • ►  June (11)
    • ►  May (16)
    • ►  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