| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: How to recognize which tasks are for GPU |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi guys,
regarding the recent release of the Conquer Cancer project GPU compute option...how can I distinguish if the computation is running on GPU or CPU? I see a list of waiting tasks in Boinc manager but not even from their names could be seen if the task is going to be crunched on GPU or CPU. Is there a way how to see which tasks are intended for GPU and which are for CPU? I have the option to send GPU tasks enabled in my profile. Thanks |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's various places to see, such as in the Task Manager of Windows where opencl or ati or nvidia is included in the process name or in BOINC Manager... it's the version number 656 or 6.56. The CPU version is 6.42 (On Windows).
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's a bug BTW in the distribution per BOINC Manager [7.0.36]... something for knreed: I've got a 6.56 processing, at normal CPU speed, in High Priority [a repair job], alongside several 6.42. This is the properties screen:
---------------------------------------- Since the wingman bombed, presumably at either 100%, or misidentified by the validators, the original got an "error" rating. There's though hope, as it went oout per the result log with too many exits [a system too busy indicator] Result Log Result Name: X0960069541265200605241218_ 1-- <core_client_version>6.10.17</core_client_version> <![CDATA[ <message> too many exit(0)s </message> ]]> Quorum: X0960069541265200605241218_ 2-- - In Progress 10/12/12 09:38:35 10/15/12 04:50:35 0.00 0.0 / 0.0 <Mine, computing now. X0960069541265200605241218_ 1-- 656 Error 10/12/12 09:35:14 10/12/12 09:38:27 0.00 33.3 / 0.0 X0960069541265200605241218_ 0-- - In Progress 10/12/12 09:35:12 10/19/12 09:35:12 0.00 0.0 / 0.0 The result that bombed shows no runtime, but that's likely having origin in the too many exits. edit: The dozen or so other HCC1 are listed with version 6.42 in BOINC Manager, so they seem to be fine. None of these are repairs, all originals. [Edit 1 times, last edit by Former Member at Oct 12, 2012 10:47:25 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
To follow up, the mislabeled HCC-CPU task did not get dismissed outright... log normal:
X0960069541265200605241218_ 2-- 656 Pending Validation 10/12/12 09:38:35 10/12/12 11:35:01 1.72 36.4 / 0.0 X0960069541265200605241218_ 1-- 656 Error 10/12/12 09:35:14 10/12/12 09:38:27 0.00 33.3 / 0.0 X0960069541265200605241218_ 0-- - In Progress 10/12/12 09:35:12 10/19/12 09:35:12 0.00 0.0 / 0.0 The wait is on the original... will it get 6.42 or 6.56 marked... likely 656 given that's what the _1 copy had. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's various places to see, such as in the Task Manager of Windows where opencl or ati or nvidia is included in the process name or in BOINC Manager... it's the version number 656 or 6.56. The CPU version is 6.42 (On Windows). Does it mean that tasks named Help Conquer Cancer 6.56 are automatically for GPU? Having a quick look at the list all tasks for this project are version 6.56 in my list, thus all are being crunched by GPU? Righ now I am on a Mac, so no opencl in the task manager, but I can see "ps" list. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, this baffles, as there wont be a Mac/Linux version of HCC-GPU for a little, in short you should not be seeing 6.56 on Mac, but if you look at my posts above, the system may be a little confused in version tagging. First there has to be code porting to OSX/Linux and alpha/beta testing and that I don't see happening until there's some good production numbers that raise the confidence level to very high.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ok, got it. Let's wait if the GPU proves itself on windows first.
Good to know. This was not mentioned in the press release. Thanks |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The CPU versions keep arriving with v 6.56 and the executable and ancillary fixed files are in fact now all listed as 6.56, so guess with greater certainty, that the techs decided without telling, an app_plan alignment needed to be made so older clients would not start deleting the 6.42 application soon as there were no HCC tasks for the CPU and redownloading them again and again each time the "no buffered tasks for CPU" occurs. It's to me wurscht, but how the science apps for GPU and CPU could get confused ... oh well, got no time to waste on that. Being told what's done in such cases as this would have saved me more [free] time.
|
||
|
|
swiftmallard
Advanced Cruncher Joined: Apr 6, 2010 Post Count: 115 Status: Offline Project Badges: 
|
Is there a way to receive only GPU WUs?
|
||
|
|
Bearcat
Master Cruncher USA Joined: Jan 6, 2007 Post Count: 2803 Status: Offline Project Badges: 
|
I tried with the suggestions mentioned but it doesn't work for me. I still get most GPU than CPU wu's. Knreed replied to me earlier that they are talking about this now if to implement it for the next GPU project. Would help allot if it was done on this one though.
----------------------------------------
Crunching for humanity since 2007!
 |
||
|
|
|