Welcome to MilkyWay@home

Posts by Wade Tregaskis

1) Questions and Answers : Preferences : Rarely getting any GPU work (Message 72372)
Posted 31 Mar 2022 by Wade Tregaskis
Post:
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.:


Thu 31 Mar 09:17:04 2022 | Milkyway@Home | [sched_op] Starting scheduler request
Thu 31 Mar 09:17:04 2022 | Milkyway@Home | Sending scheduler request: To fetch work.
Thu 31 Mar 09:17:04 2022 | Milkyway@Home | Requesting new tasks for CPU and AMD/ATI GPU
Thu 31 Mar 09:17:04 2022 | Milkyway@Home | [sched_op] CPU work request: 4697394.12 seconds; 0.00 devices
Thu 31 Mar 09:17:04 2022 | Milkyway@Home | [sched_op] AMD/ATI GPU work request: 345600.00 seconds; 1.00 devices
Thu 31 Mar 09:17:07 2022 | Milkyway@Home | Scheduler request completed: got 0 new tasks
Thu 31 Mar 09:17:07 2022 | Milkyway@Home | [sched_op] Server version 713
Thu 31 Mar 09:17:07 2022 | Milkyway@Home | No tasks sent
Thu 31 Mar 09:17:07 2022 | Milkyway@Home | Project requested delay of 91 seconds
Thu 31 Mar 09:17:07 2022 | Milkyway@Home | [sched_op] Deferring communication for 00:01:31
Thu 31 Mar 09:17:07 2022 | Milkyway@Home | [sched_op] Reason: requested by project

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.:


Thu 31 Mar 09:38:06 2022 | Milkyway@Home | Not requesting tasks: don't need (CPU: ; AMD/ATI GPU: job cache full)
Thu 31 Mar 09:38:06 2022 | Milkyway@Home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
Thu 31 Mar 09:38:06 2022 | Milkyway@Home | [sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices

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.




©2024 Astroinformatics Group