Only CUDA new work???? |
![]() |
| log in |
Message boards : Number crunching : Only CUDA new work????
1 · 2 · Next
| Author | Message |
|---|---|
|
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 · | |
|
Five Minutes ago i got 44 Workunits for my CPU... | |
| ID: 1053935 · | |
|
Dunno what's up with that.....maybe just the luck of the draw from the scheduler. | |
| ID: 1053956 · | |
|
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. | |
| ID: 1053961 · | |
|
| |
| ID: 1053962 · | |
I think you are correct, in that the work is not marked for GPU or CPU when split (possibly excepting work that is tagged as VLAR, if that function is still active). But if the host asks for both GPU and CPU work, 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. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1053965 · | |
But if the host asks for both GPU and CPU work (in the same request), 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 · | |
|
Sorry, I can only do part of the answer. | |
| ID: 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. | |
| ID: 1053999 · | |
|
Bit off topic, haven't seen any Work Units, MB nor AP, lately, but it's still 'early', in Berkeley. | |
| ID: 1054001 · | |
Bit off topic, haven't seen any Work Units, MB nor AP, lately, but it's still 'early', in Berkeley. I think you are dealing with Boinc project debt issues..... My rigs are getting work here and there as they make several requests. However, it is being sent out as fast as it is being split, so some rigs are getting very little. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1054003 · | |
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 · | |
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? That would make sense, Joe. My top rig has twice the GPU power as the #2 rig, which was getting some CPU work sent. So the top rig was only getting GPU requests filled. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1054033 · | |
|
Some further info: | |
| ID: 1054037 · | |
Some further info: The old rescheduler does not work with the current WUs and Lunatics apps. And I miss the % allocation option as well. It would be a nice addition. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 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 · | |
|
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. | |
| ID: 1054149 · | |
|
I just received an astropulse...now I have cudas , enhanced and astropulse. | |
| ID: 1054168 · | |
|
I just got a couple of cpu units marked vlar so the separation of vlars to the cpus is still turned on. | |
| ID: 1054177 · | |
|
Strange, since I let my GPU's also work at PrimeGrid I do not get *any* CUDA work? | |
| ID: 1054230 · | |
Message boards : Number crunching : Only CUDA new work????
| Copyright © 2013 University of California |