Windows 2000 Support

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

Sunday, 26 December 2010

I/O Priority Control

Posted on 23:40 by Unknown
Users have been requesting I/O priority control ever since Vista was released. I always give the same answer - the I/O priority is derived from the calling thread's priority, which is in-turn derived from the process priority class (base priority) that Process Lasso's ProBalance adjusts. In other words, the CPU priority becomes the I/O priority.

This is what Microsoft recommends - simply changing the CPU priority of the calling thread or entire process. That is why they provided no direct way to change it, and why you see no way to change it in the popular Process Explorer utility from SysInternals (now arm of Microsoft).

However, since users wanted the control to set the I/O priority, I have implemented it. Since all of Process Lasso is low-level code, it was a quick and easy implementation. You will be disappointed to discover though that there are only TWO usable levels. That's right, two. Either it is Normal or Very Low. Those are your only options.

UPDATE: It appears that support exists for High and Low as well, though I'm still determining if this support is only superficial, or if it was added at some point. I will report more later.

You might as well set the priority class to Idle to achieve the same effect most of the time, but in rare situations where you desire the CPU priority to be different than the I/O priority, I have facilitated this starting in v4.09.06 beta. In v4.09.05 beta I show the I/O priorities, and the next beta I will allow manipulation of them. This next beta is likely coming within hours.

I wrote more on this here: http://www.bitsum.com/pl_io_priority.php
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...
  • 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...
  • 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...
  • 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 ...
  • 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 ...
  • CPU Parking revisited: How to enable or disable CPU Parking yourself without registry edits
    This post has been superceded by this newer, better, and more up to date one.. including a new freeware utility called ParkControl that can ...

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)
      • Taking it up a notch with v4.1
      • v4.09.08 beta - More I/O priority levels (for expe...
      • v4.09.07 beta - Default I/O priorities now impleme...
      • I/O Priority Control
      • New low-level optimization further lowers CPU util...
      • Process Lasso Pro Commercial Licenses sales switch...
      • BETA language woes being fixed in new upload
      • Language lost in last BETA? No worries, fix coming...
      • New Portable Edition beta released, but we're gonn...
      • New Portable Edition in final stage internal testing
      • New update mechanism being coded
      • v4.1 beta coming - New logical core avoidance (avo...
      • When almost free isn't enough
      • Process Lasso enters China, Singapore, Hong-Kong, ...
      • v4.00.28
      • v4.00.26 - Fixing a GUI bug seen in XP throughout v4
      • v4.00.25 released
      • New minor update coming soon
      • Why the update checker says there is no update whe...
      • Updated Terminal Server guidance
      • Blog Update
      • Why you should *never* use a cracked copy of Proce...
      • Tying up loose ends on the activation system
    • ►  November (34)
    • ►  October (38)
    • ►  September (17)
    • ►  August (19)
    • ►  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