| 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: 3
|
|
| Author |
|
|
cw64
Advanced Cruncher Joined: Oct 6, 2007 Post Count: 120 Status: Offline Project Badges:
|
This may, or may not be BOINC related:
----------------------------------------If I run on less than 100% cores (and possibly on 100% as well) the tasks will constantly change CPU affinity (or vice versa). This must be a waste of resources. If I try to manualy assign CPU's via the task manager Windows (7x64) will soon set each one back to all CPU's. Besides, even if the change persisted I would have to assign each new task in turn. Anything I can do to stop this? ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello cw64,
Not really. The OS is designed to operate this way. Trying to fight against the OS is just an exercise in frustration. Lawrence |
||
|
|
Art_Brown
Cruncher Joined: Aug 24, 2007 Post Count: 7 Status: Offline Project Badges:
|
Good News!
You can now automatically set both the affinity and priority of BOINC (and other) processes (tasks) using an excellent free (for home and academic users) utility developed by Jeremy Collake at Bitsum Technologies called Process Lasso. Download it at http://bitsum.com/prolasso.php in 32- and 64-bit versions. Also see the thread "How can I limit WCG 2 tasks on a 4-core processor?" for the details on how I use it. Art Brown |
||
|
|
|