| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I need manuals on how to change it with regedit or other tool.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This can be done using ThreadMaster at http://bednorz.uni2.net/anyland/threadmaster/threadmaster.htm which describes using regedit to change percentage utilization in its FAQs. Regedit is a scary Windows utility which assumes some expertise on the part of the user. There are all sorts of cautions, some of which (like back up your Registry) are not very useful if the Registry is damaged severely.
If you use Google, you can find much additional information about using regedit, such as http://www.robvanderwoude.com/index.html My opinion - use at your own risk. First try for a registry cleanup, using freeware. Then if all is well, try using regedit to create a backup. Then try finding the ThreadMaster HKEY entry and make sure you understand it. Only then try changing it. Incidentally, Motherboard Monitor is a useful utility to find out just how hot your CPU is. After decades of using computers, I am surprised to discover how many people are interested in under utilizing their computer. I take for granted that heat issues are a hardware problem that needs fixing, but - live and learn! - I am discovering that some people prefer to reduce utilization. I am not experienced since I have never done this myself. Good luck, Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I need manuals on how to change it with regedit or other tool. cmd /c start /High ud.exe Again I would urge caution. Use at your own risk. The underlying agent does a pretty good job of grabbing 100% CPU when nothing else needs it and making way when something else needs the CPU. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The priority of the grid agent is normally 1, the same as the idle process. The lowest priority that can be accessed through Task Manager is 2. This argues that a system call is embedded in the ud.exe agent that will reset anything done through the Task Manager or the cmd interface. This is just a guess on my part.
Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ud.exe runs at normal priority on my machine. It spawns a sub process called ud_xxxxx.exe (where xxxxx is a set of digits). This has an idle priority. This in turn then spawns WCGrid_Rosetta.exe which also has an idle priority.
For a test I used Process Explorer from sysinternals and changed the priority on ud_xxxxx.exe and WCGrid_Rosetta.exe to Normal and they stayed there. Watching the process stack shows that it made no difference on my laptop about how much CPU was allocated. |
||
|
|
|