Message boards : BOINC Manager : Processor affinity mask
Message board moderation
Author | Message |
---|---|
Send message Joined: 17 Feb 13 Posts: 13 |
Hi, I would like to crunch some BOINC projects and play games on Facebook at the same time. Unfortunately BOINC consumes all CPU, so these games slows very much. In addition to limiting CPU count and CPU usage I also changed processor affinity mask using Task Manager (on Windows), and looks that this aiso helped me a bit. Could you change BOINC Manager so it would automatically do this based on configured CPU count limit? |
Send message Joined: 29 Aug 05 Posts: 15573 |
Won't be done. As: a) it isn't a function of BOINC Manager. That is just a graphical user interface to allow you to command and control the BOINC client program. b) even if CPU affinity were to be added to the BOINC client program, tests in the past have shown that there is no real decrease in run times. If it were 10% and more, things would be different, but for 2-4% it's not really affordable to spend the programming and debugging time on it. Also, something like that would need to use an API of sorts, one that needs to be available for Windows, Linux and Mac OSX at the minimum. Adding a feature to be used by just one operating system pool isn't in BOINC its interests. Apart from that, you can set BOINC to use the amount of CPU cores you want it to use before you go game. |
Send message Joined: 23 Feb 12 Posts: 198 |
I don't know all of the details or technical issues involved. But I know one of my team members had done some work with affinity under Linux and found a pretty huge speed gain. I honestly don't know what all he did. I'm not that smart...but the results he shared 4 years ago looked worth while. http://boinc.berkeley.edu/trac/ticket/853 And he has a Linux setup detailed for use on multi socket machines in our forums here: http://hardforum.com/showthread.php?t=1805578 Please excuse me if this is completely off topic... |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.