Wednesday, July 1, 2009
Hardware/software Tip to limit CPU usage per appl
ThreadMaster monitors all running applications, and detects when a application starts to use excessive processor resources. It dynamically hunt down the offending thread, and clamp the CPU for this thread. This feature ensures that other users can remain working without noticing anything. The clamped process will eventually finish, and the clamp will be removed automatically. ThreadMaster is a background service implementing a CPU Quota mechanism on top of the standard thread scheduling algorithms of the Microsoft Windows 2000 Operating Systems. Administration of ThreadMaster is extremely simple, the behavior is in general, controlled by only two key parameters. The first parameter instructs ThreadMaster to monitor application activity over a given of time. The second parameter is the allowed max. average CPU utilization for the process over the defined time. Note, please look the readme.txt before installing, so you can tweak as you like. BES is a small tool which limits the CPU usage for a specified process: for instance, you can limit the CPU usage of a process which would use CPU 100%, down to 50% (or any percentage you like). With this, you can use other programs comfortably while doing something CPU-intensive in the background. By limiting the CPU load, you can also cool down your CPU immediately when it happens to get too hot. Of course the processing speed will slow down proportionally if you limit the CPU usage, but it should be much better than crashing because of heat or (in the worst scenario) having your computer broken with a burned CPU. Furthermore, BES can hide any windows you don't want to be seen for some reason, without killing the process, and restore the hidden windows again anytime you like. Note, same purpose, but with GUI & maybe some extras. Hope is use-full, locally using ThreadMaster with no issues. Please read carefully, and remember to exclude some applications which may need 100% utilization, for others we will have to find our sweet-spot depending of the system CPU capacities. In our setup Rambus uses a limit of 50% after ThreadMaster is limiting (in case it wants all), and WinLogon.exe is not excluded, due to past issues. Choose wisely & have free fun. OS requirements are 2000/XP.
Subscribe to:
Post Comments (Atom)

No comments:
Post a Comment