| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Setting for 'Run ONLY GPU tasks'? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges: 
|
I'm using BOINC 7.0.36 and find on a system running ONLY GPU tasks that I am still being sent CPU tasks. BOINC doesn't seem to be aware that the CPU tasks aren't being processed and keeps pulling in new ones during new updates meaning that I have to abort them to stop my cache from being choked up.
----------------------------------------I am still using app_info and wonder if I should be disabling CPU use (but wouldn't that imply that CPU tasks couldn't be processed too because CPU is required for start and finish as well as processing of the first image and switching to the second?) Do later versions of BOINC address this issue? As a footnote, this issue doesn't only pertain to GPU-exclusive systems. A system running 90% GPU tasks can pull in far more CPU tasks than could ever be processed (sometimes 50-50 ratio CPU to GPU tasks), so I am wondering if there is something in my config that needs to be addressed.  Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am still using app_info and wonder if I should be disabling CPU use (but wouldn't that imply that CPU tasks couldn't be processed too because CPU is required for start and finish as well as processing of the first image and switching to the second?) Setting "Allow research to run on my CPU?" to "No" does not affect WUs in cache. It only prevents you from downloading new CPU WUs. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
.36... what a release that was to quickly pass by :D Get on the app_config.xml bandwagon through a version of 7.0.40 or higher [am using 7.0.52 now, which has a major work-fetch fix at that]. It's so much simpler to configure than app_info [as advertised widely being spread by word of mouth, made illegal at WCG in the near future **].
As per rr967, the device profile has an explicit option to say yes/no to receiving CPU tasks, so not sure why if you have de-selected that you would be receiving HCC-CPU tasks, or for that matter any WCG-CPU tasks. Of course the client will want to compute the CPU tasks. We need to remember that lots of options are project specific, not "global" as applying to the general operation of the client. ** Just at WCG. app_info would still work at other projects, until they... |
||
|
|
|