Message boards :
BOINC roadmap / wish list
Posted 28 Mar 2020 by Ghost Rider 51
I started using Boinc with a single core CPU. Switching projects was the only way to participate in multiple projects. There was a drawback. Sometimes a task was almost finished to report it in time before the deadline and then projects were switched :-(
There already is the ability to select how many cores/threads each project can use.
The app_config.xml file you create in the projects home directory can do that. Look at the manual here https://boinc.berkeley.edu/wiki/Client_configuration to see how.
Message boards :
Questions and problems :
GPU idling just because I set from 10 days to 1 day of work storage
Posted 3 Nov 2019 by Ghost Rider 51
perhaps you might like to mention the ones you selected rather than the ones you didn't
I wonder if, because you have 2 GPUs that are different (980 and 1080), maybe one empties it's queue faster than the other (and the work units are different). Then, because the remaining work for the one still active is more than the 1 day limit you set, boinc may be delaying sending work until both GPUs are less than the set amount before it will send more work for the idle one.
I had a similar situation when crunching for 2 different projects in that boinc did not seem to ever balance the load between the projects. It would seesaw back and forth from doing work on one project 100% of the time to doing work on the other project 100% of the time and never was able to balance it (on one machine).
My solution was to dedicate one machine to one project and another to the other project.
It could be doing the same for the different GPUs. Maybe if those GPUs were in different hosts this conflict would not occur.
I agree that load balancing should be a developer priority.
Copyright © 2020 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.