Rarely getting any GPU work
Questions and Answers :
Preferences :
Rarely getting any GPU work
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 17 Mar 10 Posts: 1 Credit: 19,785,985 RAC: 0  
|
MilkWay@home seems very unwilling to provide my computer with GPU work units (sometimes it won't provide CPU ones either). My GPUs sit idle most of the time - or, if I have Einstein enabled, it uses them instead. Einstein@home seems to have absolutely no problem giving me work. I've searched these forums and tried all the suggested workarounds, but none of them have any effect (or don't apply, e.g. custom Windows BOINC clients; I'm using a Mac). I do see the common problem that the client refuses to request GPU work units if it has any already, ("N seconds; 0.00 devices" in the logs). But even when it does request units, and has none locally nor any to submit, it still almost always gets none, e.g.:
If I leave it running for many days, I occasionally see it actually grab some work units - but usually just a dozen or two, which last all of about twenty minutes. Sometimes it refuses to get any tasks because it claims the "job cache [is] full", which is weird because often when that happens I have fewer CPU tasks downloaded than available cores - i.e. definitely more room; CPU going idle - and no GPU tasks. e.g.:
It's a shame because MilkyWay@home seems like an interesting project, and it seems to like my GPU (Vega64) a lot more than Einstein@home - about a hundred-fold difference in credit per GPU-second, with tasks taking a minute or so instead of several hours. |
|
Send message Joined: 13 Dec 17 Posts: 46 Credit: 2,421,362,376 RAC: 0  
|
Yes, many people experience similar problems (erratic WU supply). The reason is that there were some issues with the project server recently (see https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4863 and the other related threads in the News section). As far as I can tell the issues are not yet completely resolved but there should be steadier WU supply now. All best |
 mikey Send message Joined: 8 May 09 Posts: 3339 Credit: 524,010,781 RAC: 0   
|
[quote]MilkWay@home seems very unwilling to provide my computer with GPU work units (sometimes it won't provide CPU ones either). My GPUs sit idle most of the time - or, if I have Einstein enabled, it uses them instead. Einstein@home seems to have absolutely no problem giving me work. I've searched these forums and tried all the suggested workarounds, but none of them have any effect (or don't apply, e.g. custom Windows BOINC clients; I'm using a Mac). I do see the common problem that the client refuses to request GPU work units if it has any already, ("N seconds; 0.00 devices" in the logs). But even when it does request units, and has none locally nor any to submit, it still almost always gets none, e.g.: [quote] Another problem MilkyWay has is a 10 minute back-off between the last gpu being run and new ones being sent to us, a previous Admin did it and the current Admins can't seem to find the setting, the easy answer is to do what you are already doing which is to crunch some Einstein units in between batches of MW units. If you increase your cache size you will get more gpu tasks in a batch, upto the limit, but in your case it would also mean more cpu tasks and that could be a problem getting them back on time as Boinc does not have a separate setting for cpu and gpu tasks at the same project. |
Keith Myers Send message Joined: 24 Jan 11 Posts: 715 Credit: 556,864,830 RAC: 43,467  
|
Ping the project with an Update every 15 minutes or shorter automatically. Scripting can be done in Linux and Windows. watch -n 300 ./boinccmd --project http://milkyway.cs.rpi.edu/milkyway/ update 
|
|
Send message Joined: 14 Dec 22 Posts: 3 Credit: 113,680,284 RAC: 0  
|
I have a similar issue. I built a whole machine just for Milkyway with a 5900X and a Radeon Pro VII (6.528 TFLOPS FP64) that finishes the stack of 300 separation GPU tasks in around 40 minutes doing 6 concurrent tasks. After that, even with Milkway as the only enabled project, it just runs CPU tasks, even after the 10 minute runoff time that I see in "properties" of the project in BOINC Manager that I don't understand. The only way for me to get more tasks is to hit update on the porject after all 300 have been completed. I've combed through the documentation for app_config.xml and cc_config.xml to see if there were any serttings for mandating updates or something, but couldn't find anything. Is this a temporary issue with Milkway or do you have any other advice for keeping a constant stream of GPU tasks fed to my GPU? Best, Eric 
|
|
mikey Send message Joined: 8 May 09 Posts: 3339 Credit: 524,010,781 RAC: 0
|
I have a similar issue. I built a whole machine just for Milkyway with a 5900X and a Radeon Pro VII (6.528 TFLOPS FP64) that finishes the stack of 300 separation GPU tasks in around 40 minutes doing 6 concurrent tasks. After that, even with Milkway as the only enabled project, it just runs CPU tasks, even after the 10 minute runoff time that I see in "properties" of the project in BOINC Manager that I don't understand. The only way for me to get more tasks is to hit update on the porject after all 300 have been completed. I believe there is a limit of 300 tasks per day per device |
 Send message Joined: 19 Jul 10 Posts: 627 Credit: 19,363,599 RAC: 3,478 
|
I believe there is a limit of 300 tasks per day per device Not per day, just per GPU, when you return some of them, you can get new ones, you are just not allowed to have more than 300 in your cache. 
|
©2024 Astroinformatics Group