| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: The 'GPU' and the 'CPU' qualifier for a GPU+CPU world |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
With the coming WCG GPU-aware WUs, what used to be, say, 'task', would be ambiguous in the coming GPU+CPU world of WCG. We would need a qualifier, thus: 'CPU task', or 'GPU task' rather than the plain 'task'.
BOINC_v6.10.58 seems to be not aware of this. In my Intel32Vista crunching HCMD2 exclusively, the following 4-line text snip shows: [line01] update requested by user [line02] Sending scheduler request: Requested by user. [line03] Reporting 5 completed tasks, requesting new tasks for GPU [line04] Scheduler request completed: got 0 new tasks -- Line03 is a request for a GPU task, which is in error for the following reasons: a] Currently, there is no option to elect to receive GPU tasks. b] I have not explicitely stated that I want to receive GPU tasks. c] There is no GPU task currently available for any WCG project. -- Line04 is ambiguous ('tasks' assumed as 'CPU tasks'), and in combination with the erroneous line03, made confusing. Notice how things become crystal clear with the CPU qualifier: [line05] CPU tasks update requested by user [line06] Sending scheduler request for CPU: Requested by user. [line07] Reporting 5 completed CPU tasks, requesting new CPU tasks [line08] Scheduler request for CPU completed: got 0 new CPU tasks It is more likely that the user-update-request cycles for CPU tasks and that for GPU tasks will be asymmetrical, which will require a separate process for a CPU and that for a GPU -- another justification of the need for a 'CPU' or 'GPU' qualifier. Thus, for the GPU part: [line09] GPU tasks update requested by user [line10] Sending scheduler request for GPU: Requested by user. [line11] Reporting [X] completed GPU tasks, requesting new GPU tasks [line12] Scheduler request for GPU completed: got [Y] new GPU tasks How WUs for CPUs and those for GPUs will be named is another part of the nomenclature work. There is a potential for getting into a messy situation that may be difficult to correct later if the nomenclature is not thoroughly worked out. ; |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
andzgrid,
----------------------------------------This is kind of moot, since Berkeley has moved on and is seemingly not far off from releasing 7.0.x as successor to 6.12.x. The 6.10.58 client is a dead duck for development. There is a 6.10.60 for those who want to use the 6.10 series with non critical fixes. With 6.10.58 what is currently seen is a request of GPU work [when manually updating] with a back-off clock being kicked by the WCG servers for 14 days to not request for GPU again until the clock expires, or is reset by a manual update. The message is not shown when the GPU function of BOINC has been disabled in the cc_config.xml with the <no_gpus>1</no_gpus> option. The 6.10.58 client has a separate scheduler for CPU and GPU and has kind of been ground up rewritten in 7.0.x, so those who like it messaged better can upgrade to 6.12 or even 7.0. At any rate, the WCG servers will be ready when a GPU based science launches. That said, my understanding is, that there is no need to upgrade the client. 6.10.58 will work fine WCG science app release for NVidia and ATI/AMD cards. Obviously, GPU crunching will be opt-in, and commented elsewhere, surely the CPU version for the same science could be opted out. --//-- P.S. This is the message series when hitting update on WCG with GPU disabled on a 7.0.2 test client I'm running (scheduler is far from stable): 3087 World Community Grid 12-12-2011 23:14 update requested by user 3088 World Community Grid 12-12-2011 23:14 [sched_op] Starting scheduler request 3089 World Community Grid 12-12-2011 23:14 Sending scheduler request: Requested by user. 3090 World Community Grid 12-12-2011 23:14 Not reporting or requesting tasks 3091 World Community Grid 12-12-2011 23:14 [sched_op] CPU work request: 0.00 seconds; 0.00 CPUs 3092 World Community Grid 12-12-2011 23:14 Scheduler request completed 3093 World Community Grid 12-12-2011 23:14 [sched_op] Server version 601 3094 World Community Grid 12-12-2011 23:14 Project requested delay of 11 seconds 3095 World Community Grid 12-12-2011 23:14 [sched_op] Deferring communication for 11 sec 3096 World Community Grid 12-12-2011 23:14 [sched_op] Reason: requested by project [Edit 1 times, last edit by Former Member at Dec 12, 2011 10:18:59 PM] |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
We will be adding a opt-in feature for GPU tasks. This will be controlled server side. So while your client may ask for GPU tasks, it will not receive them unless you have opted-in. This opt-in will apply for both beta and production apps. The option will be on the My Projects page and will also be on the device profile page.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
When can we expect to see these GPU options settings appearing?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Right around when the Beta comes ;>)
--//-- |
||
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges: 
|
Right around when the Beta comes ;>) --//-- So, are we still on schedule for Jan.? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Whoever posted about Jan. would have to answer that.
--//-- |
||
|
|
|