Only CUDA new work????

Message boards : Number crunching : Only CUDA new work????

Author	Message
jravin Send message Joined: 25 Mar 02 Posts: 717 Credit: 61,408,953 RAC: 70,760	Message 1053934 - Posted: 8 Dec 2010, 15:37:02 UTC
	I am getting new work for both my 8-core, 4 GT240 machines now (THANKS to the powers-that-be!) but I am only getting CUDA, even though my machines have asked for both (BOINC 6.10.56). Any idea why this might be? Is the project only generating CUDA WUs for now? ____________
	ID: 1053934 ·

Helli Volunteer tester Send message Joined: 15 Dec 99 Posts: 692 Credit: 66,782,187 RAC: 2,424	Message 1053935 - Posted: 8 Dec 2010, 15:38:38 UTC - in response to Message 1053934.
	Five Minutes ago i got 44 Workunits for my CPU... Helli ____________
	ID: 1053935 ·

SciManStev Volunteer tester Send message Joined: 20 Jun 99 Posts: 4297 Credit: 63,069,476 RAC: 73,574	Message 1053961 - Posted: 8 Dec 2010, 16:50:37 UTC
	Same thing happened to me, but it seems to have settled out now. I even loaded more Einstein last night to keep my chiller from cycling. Steve ____________ Warning, addicted to SETI crunching! Crunching as a member of GPU Users Group. GPUUG Website
	ID: 1053961 ·

BilBg Send message Joined: 27 May 07 Posts: 2023 Credit: 3,047,717 RAC: 6,639	Message 1053962 - Posted: 8 Dec 2010, 16:51:35 UTC - in response to Message 1053934. Last modified: 8 Dec 2010, 17:00:51 UTC
	I don't think the tasks splitters produce are marked CUDA or CPU - only after you (or anybody) ask for particular type of tasks (and successfully get them) they are "marked" accordingly. (The task (WU) file is the same for CUDA or CPU, only the info about it in client_state.xml is different. If you look how Reschedulers work to "move" tasks CPU <--> GPU you will see that only the client_state.xml is changed - not the tasks/WUs files. ) ____________ - ALF - "Find out what you don't do well ..... then don't do it!" :)
	ID: 1053962 ·

BilBg Send message Joined: 27 May 07 Posts: 2023 Credit: 3,047,717 RAC: 6,639	Message 1053975 - Posted: 8 Dec 2010, 17:20:02 UTC - in response to Message 1053965.
	But if the host asks for both GPU and CPU work (in the same request), I think it's the scheduler that then marks them as one or the other and decides which work request to fill when they are assigned to a host and sent. We'll wait for Richard Haselgrove and/or Josef W. Segur to shed some light on how the (server) scheduler decides on that matter ... :) ____________ - ALF - "Find out what you don't do well ..... then don't do it!" :)
	ID: 1053975 ·

Richard Haselgrove Volunteer tester Send message Joined: 4 Jul 99 Posts: 7462 Credit: 39,752,773 RAC: 34,222	Message 1053997 - Posted: 8 Dec 2010, 18:09:12 UTC - in response to Message 1053975.
	Sorry, I can only do part of the answer. Certainly, the WUs themselves are not differentiated: any WU, once split, could be allocated to a CPU, a CUDA card, or any other type of processor for which an application exists. I would imagine that the rule under which a vlar WU is not assigned to a CUDA processor is still in force, but that's an allocation decision, not any fundamental property of the WU itself. Look at your task list: I'm sure you'll easily be able to find WUs where the two identical replicated tasks (_0 and _1) are allocated, one to CPU and the other to CUDA. I'll have to leave it to Joe to explain, if he can, why the scheduler faced with a request for both CPU and GPU shows a strong tendency to give up after filling only the GPU part of the request.
	ID: 1053997 ·

Metod, S56RKO Volunteer tester Send message Joined: 27 Sep 02 Posts: 309 Credit: 23,958,922 RAC: 21,622	Message 1053999 - Posted: 8 Dec 2010, 18:18:46 UTC - in response to Message 1053997.
	My guess about why scheduler prefers GPU over CPU: GPU will work through task much more efficiently and faster. If scheduler doesn't have enough tasks to fill up both GPU and CPU queues, then it's more than sensible to fill the more effective queue first. My GPU host can't get enough tasks while some other CPU-only hosts have better luck. ____________ *Metod ...*
	ID: 1053999 ·

Fred J. Verster Volunteer tester Send message Joined: 21 Apr 04 Posts: 3232 Credit: 31,585,541 RAC: 1	Message 1054001 - Posted: 8 Dec 2010, 18:25:10 UTC - in response to Message 1053997.
	Bit off topic, haven't seen any Work Units, MB nor AP, lately, but it's still 'early', in Berkeley. Einstein has given out too much work on 2 QUAD's (Q6600+GTS250&X9650+GTX480) and GPUgrid, that most of their tasks running High Priority, maybe I've to set N.N.T. for Einstein,(looks like 'abuse') :( But glad new severs are in place and in due time work will come, I hope, atleast. ____________ Knight Who Says Ni N!, OUT numbered.................
	ID: 1054001 ·

Josef W. Segur Volunteer developer Volunteer tester Send message Joined: 30 Oct 99 Posts: 3932 Credit: 934,327 RAC: 15	Message 1054029 - Posted: 8 Dec 2010, 19:06:49 UTC - in response to Message 1053934.
	I am getting new work for both my 8-core, 4 GT240 machines now (THANKS to the powers-that-be!) but I am only getting CUDA, even though my machines have asked for both (BOINC 6.10.56). Any idea why this might be? Is the project only generating CUDA WUs for now? When your host asks for both kinds of work, the Scheduler sends work for the "best" application first and only after that part of the request is fulfilled will it send work for other application[s]. So with a limited amount of tasks available, probably the GPU request is not being fully satisfied and the Scheduler never goes on to send some to the CPU. Joe
	ID: 1054029 ·

jravin Send message Joined: 25 Mar 02 Posts: 717 Credit: 61,408,953 RAC: 70,760	Message 1054037 - Posted: 8 Dec 2010, 19:19:10 UTC
	Some further info: I tried to use the old rescheduler (1.9) to reschedule some GPU -> CPU, but it foumd 0 WUs...is this an artifact of running > 1 Project? It always worked before, but I was only running SETI at the time. The "new" Rescheduler worked just fine, however. One question - it doesn't seem to have the option, as the old one did, of rescheduling % of WUs to GPU/CPU...did I miss something? ____________
	ID: 1054037 ·

JohnDK Send message Joined: 28 May 00 Posts: 756 Credit: 20,536,129 RAC: 35,546	Message 1054048 - Posted: 8 Dec 2010, 19:51:04 UTC - in response to Message 1054038.
	The old rescheduler does not work with the current WUs and Lunatics apps. Old rescheduler still works if you edit app_info so it only have the <version_num>608 sections. I'm still using it although there's almost never any vlars send to gpu anymore. btw be careful editing app_info if you have 609 tasks running, they will disappear from Boinc, finish all gpu work first :)
	ID: 1054048 ·

-BeNt- Send message Joined: 17 Oct 99 Posts: 1234 Credit: 10,116,112 RAC: 0	Message 1054149 - Posted: 9 Dec 2010, 1:46:18 UTC
	At this point in time I'm not going to complain about what work I have, I'm just happy I have work. As I sit now I have a bit over 300 wu's on both my machines. All of it appears to be cuda. Ah well the new quad will have to wait a bit to warm up I guess. ____________ Traveling through space at ~67,000mph!
	ID: 1054149 ·

Proyecto Unity Send message Joined: 13 Mar 03 Posts: 6 Credit: 3,520,548 RAC: 0	Message 1054168 - Posted: 9 Dec 2010, 4:52:43 UTC
	I just received an astropulse...now I have cudas , enhanced and astropulse. ____________
	ID: 1054168 ·

dan Send message Joined: 18 Oct 02 Posts: 392 Credit: 13,517,023 RAC: 14,279	Message 1054177 - Posted: 9 Dec 2010, 5:26:28 UTC
	I just got a couple of cpu units marked vlar so the separation of vlars to the cpus is still turned on. ____________
	ID: 1054177 ·

Dirk Broer Send message Joined: 18 Jun 00 Posts: 14 Credit: 2,102,306 RAC: 2,180	Message 1054230 - Posted: 9 Dec 2010, 12:57:19 UTC
	Strange, since I let my GPU's also work at PrimeGrid I do not get any CUDA work? ____________
	ID: 1054230 ·

1 · 2 · Next

Message boards : Number crunching : Only CUDA new work????