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

  • 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 v3.65.3 beta released
    I've released the first new beta that is 100% UNICODE. I've regression tested almost all the software, though there may still be som...
  • 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...
  • v5.0.0.18: Fix auto updater in XP
    During testing a few hours ago I noticed the auto-update was failing in some XP installations. Specifically, it would appear to stall at the...
  • 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...
  • One bit of bad news, one bit of good news
    One disappointing thing is that I've decided to cancel the change history shown in the update dialog, at least for v4.1. I may add it in...
  • Version 6 Goes Final
    Version 6 Goes Final as v6.0.0.58 I don't even know where to start with the changes, so I'm going to refer you to two documents. Nei...
  • Smaller minidumps means more submissions
    One of the changes in the last build was that I reduced the size of the minidumps that are generated in the rare event of a crash. They have...
  • 5.0.0.9 beta
    Sadly, my change in version naming did confuse some users who thought v5 was final already. Well, it is close, but not there --- I am rapidl...
  • Code review and bug tracking continues
    This is the tedious part of pre-release work ;o. I will release a new beta though, as soon as I possibly can. Although I've got new prob...

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