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: 2
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is there a way to set parameters in a device profile that act only on the WCG project and not the BOINC manager as a whole?
On one particular machine my client is managing three separate projects (WCG on CPU and 2 others on GPUs). It appears that when I change settings in the relevant WCG device profile, it applies to everything the client does. What I am trying to achieve is to limit the CPU usage of WCG to reserve one or two cores for mothering the GPU WUs, however setting the "On multiprocessors use" to less than the full complement appears to throttle the whole client. The other projects have very clearly separate profiles for general BOINC preferences and specific project preferences, but WCG seems to operate as though it is an exclusive club. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Fortunately, to keep it simple and manageable, whichever project you make changes applies to all projects for all clients associated to that profile. If it would not, major conflict could develop. Also fortunately, there's the app_config.xml and cc_config.xml where a lot can be coded so that parts of a CPU is reserved to support GPGPU computing. The wiki manual is here: http://boinc.berkeley.edu/wiki/Cc_config.xml . If you search the GPU support forum you're going to find working samples of how it was done at the time of HCC1 running on GPGPU in 2013. There's a 3rd config file called app_info.xml, but WCG does not support the use of it. The app_config.xml was created to replace latter.
|
||
|
|
![]() |