Thanks for the gpu longevity answers, I'll stick with more worry free CPU's only. That's one thing I like about World Community Grid, it's CPU only.

Sorry, I wasn't meaning to scare you off. I thought you were maybe wanting to optimize their total work potential. I'm running 4 MW@H tasks per GPU and could run up to 5 or 6 if I wanted to fully load them up, but fewer tasks per GPU shouldn't load them up too much to worry about either way beyond needing to clean dust off a bit more often, if you have your computer on and are using it anyway. I can generally run 2 tasks per GPU and play games at the same time without issue, since I use V-sync or frame rate limits in the video games for 60 FPS. 1 task per GPU wouldn't be much above idle for me, expect for keeping the clock rates up.

As Peter said above, GPUs are often much more powerful at crunching than CPUs for the work units that can make use of them. You can pretty easily tell from my computer's BOINC stats in my signature which projects I've used the GPUs or CPU on. Currently I'm running 8 MW@H tasks total on the GPUs, and 8 Einstein task on the CPU. https://i.imgur.com/YgGl6Zs.png

---

Still no Nbody Simulations validated, all in Validation Inconclusive. All completed on my machine but status showing as unsent ?

Uh oh, very slow server responses again. [sending adrenaline patch]

Impossible to get any WUs for severall days now ! when will this project run again as it should ?

09/04/2022 11:22:48 | Milkyway@Home | update requested by user
09/04/2022 11:22:50 | Milkyway@Home | Sending scheduler request: Requested by user.
09/04/2022 11:22:50 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
09/04/2022 11:22:51 | Milkyway@Home | Scheduler request completed: got 0 new tasks
09/04/2022 11:22:51 | Milkyway@Home | Project requested delay of 91 seconds

Impossible to get any WUs for severall days now ! when will this project run again as it should ?

09/04/2022 11:22:48 | Milkyway@Home | update requested by user
09/04/2022 11:22:50 | Milkyway@Home | Sending scheduler request: Requested by user.
09/04/2022 11:22:50 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
09/04/2022 11:22:51 | Milkyway@Home | Scheduler request completed: got 0 new tasks
09/04/2022 11:22:51 | Milkyway@Home | Project requested delay of 91 seconds

When Tom buys SSDs.

In the meantime I set Windows Task scheduler to ask for work every 2 minutes, I have my GPUs running 80% of the time.

Back to Collatz and Einstein. Will watch and see if things get back to normal.

As Peter said above, GPUs are often much more powerful at crunching than CPUs for the work units that can make use of them. You can pretty easily tell from my computer's BOINC stats in my signature which projects I've used the GPUs or CPU on. Currently I'm running 8 MW@H tasks total on the GPUs, and 8 Einstein task on the CPU. https://i.imgur.com/YgGl6Zs.png

I'm not deterred, however once WCG is back up I'm outta here anyway so the issue is moot, plus I have a buyer for 5 decent vid cards gathering dust. The market is just too hot not to sell.

When World Community Grid has new work units i will be going back to World Community Grid at least for CPU work units and i may stay here for GPU work units.World Community Grid in the past didnt have enough GPU work units for my liking except when they had the stress test

---

PrimeGrid, GPUGrid, Einstein@home, Amicable Numbers, MLC@home all can utilize GPUs. So anyone with idling GPUs I would recommend joining one of those projects and setting the resource share to 0 on it. So when MW@Home comes back your systems will automatically switch to it.

As Peter said above, GPUs are often much more powerful at crunching than CPUs for the work units that can make use of them. You can pretty easily tell from my computer's BOINC stats in my signature which projects I've used the GPUs or CPU on. Currently I'm running 8 MW@H tasks total on the GPUs, and 8 Einstein task on the CPU. https://i.imgur.com/YgGl6Zs.png

I'm not deterred, however once WCG is back up I'm outta here anyway so the issue is moot, plus I have a buyer for 5 decent vid cards gathering dust. The market is just too hot not to sell.

Odd, I've been getting very cheap GPUs. They've dropped in price here in the UK.

P.S. why do only Americans use the word moot?

When World Community Grid has new work units i will be going back to World Community Grid at least for CPU work units and i may stay here for GPU work units.World Community Grid in the past didnt have enough GPU work units for my liking except when they had the stress test

They might have a burst because the scientists will be currently starved of results.

.No Separation tasks available

.No Separation tasks available

There are plenty of Separation tasks. 21K currently.

You need to script a project update to get tasks every scheduler connection.

If BOINC receives a no task reply for a scheduler connection, it immediately backs off for 1 hour, then progressively adds more backoff hours to get to 24 hours.

If you don't intercede, no wonder you aren't getting work.

---

.No Separation tasks available

There are plenty of Separation tasks. 21K currently.

You need to script a project update to get tasks every scheduler connection.

If BOINC receives a no task reply for a scheduler connection, it immediately backs off for 1 hour, then progressively adds more backoff hours to get to 24 hours.

If you don't intercede, no wonder you aren't getting work.

?????

watch -n 720 ./boinccmd --project http://milkyway.cs.rpi.edu/milkyway/ update or the equivalent in Windows Task Scheduler

---

.No Separation tasks available

There are plenty of Separation tasks. 21K currently.

You need to script a project update to get tasks every scheduler connection.

If BOINC receives a no task reply for a scheduler connection, it immediately backs off for 1 hour, then progressively adds more backoff hours to get to 24 hours.

If you don't intercede, no wonder you aren't getting work.

?????

The server is broken, nobody knows why, sometimes it can't be bothered giving you tasks even though they're there in the queue. For some reason you hid your computers so I can't tell what OS to advise you on.

Same with me. Gets GPU work from time to time but mostly the machine is idle, despite the server status showing plenty of jobs available.
I only do separation on my GPU at the moment.

Tue 12 Apr 2022 11:42:16 PM PDT | Milkyway@Home | update requested by user
Tue 12 Apr 2022 11:42:20 PM PDT | Milkyway@Home | Sending scheduler request: Requested by user.
Tue 12 Apr 2022 11:42:20 PM PDT | Milkyway@Home | Requesting new tasks for NVIDIA GPU
Tue 12 Apr 2022 11:42:22 PM PDT | Milkyway@Home | Scheduler request completed: got 0 new tasks

This is on a Linux machine with a single GPU card.

Same with me. Gets GPU work from time to time but mostly the machine is idle, despite the server status showing plenty of jobs available.
I only do separation on my GPU at the moment.

Tue 12 Apr 2022 11:42:16 PM PDT | Milkyway@Home | update requested by user
Tue 12 Apr 2022 11:42:20 PM PDT | Milkyway@Home | Sending scheduler request: Requested by user.
Tue 12 Apr 2022 11:42:20 PM PDT | Milkyway@Home | Requesting new tasks for NVIDIA GPU
Tue 12 Apr 2022 11:42:22 PM PDT | Milkyway@Home | Scheduler request completed: got 0 new tasks

This is on a Linux machine with a single GPU card.

I use Windows so I'm not sure what you need to do, but I've set up a scheduled task to ask for work every 2 minutes (since 1.5 minutes is a server limit), and I have my GPUs running most of the time. But you could try Keith's suggestion of:

watch -n 720 ./boinccmd --project http://milkyway.cs.rpi.edu/milkyway/ update

But overall this is probably just taking tasks that would have gone to other people. Tom needs to get this server working harder somehow.

But overall this is probably just taking tasks that would have gone to other people. Tom needs to get this server working harder somehow.

Valid point, but I suspect that as long as there are issues with that huge number of NBody tasks waiting there will continue to be difficulties. Lots of NBody users are clocking up huge numbers of "Validation inconclusive" results, and the retries for those will go on the end of the queue, I fear... I wonder how long it will take to get 13 million tasks out and returned?...

I don't know if there is an official mechanism that could be used to alter the order in which the feeder sends stuff out, or whether it would be possible to cancel the bulk of those excess tasks. (Of course, cancelling them would not be a good idea if they can't be recreated somehow at a later point in time.) NBody is Eric's project, not Tom's, so I guess they'll have to sort it out between them somehow.

On a related topic, I would suggest that someone writes a script that checks the number of tasks waiting to go out for each project and turns off the work generator for a project if it exceeds some pre-chosen limit, turning it back on again when the number of tasks falls below a lower limit (chosen to avoid constant stop-start) - that could then be a cron job (or equivalent) running (say) every 15 or 30 minutes. It won't solve the current problem but it would mean a recurrence could be avoided without the need for constant supervision! (I presume there isn't such a capability built into the generators already...)

Cheers - Al.

But overall this is probably just taking tasks that would have gone to other people. Tom needs to get this server working harder somehow.

Valid point, but I suspect that as long as there are issues with that huge number of NBody tasks waiting there will continue to be difficulties. Lots of NBody users are clocking up huge numbers of "Validation inconclusive" results, and the retries for those will go on the end of the queue, I fear... I wonder how long it will take to get 13 million tasks out and returned?...

I don't know if there is an official mechanism that could be used to alter the order in which the feeder sends stuff out, or whether it would be possible to cancel the bulk of those excess tasks. (Of course, cancelling them would not be a good idea if they can't be recreated somehow at a later point in time.).

The Boinc server seems to be a cobbled together piece of crap that nobody knows how to use. We all know the client sux, but the server I think is even worse.

NBody is Eric's project, not Tom's, so I guess they'll have to sort it out between them somehow..

I thought Tom was Eric's replacement?

On a related topic, I would suggest that someone writes a script that checks the number of tasks waiting to go out for each project and turns off the work generator for a project if it exceeds some pre-chosen limit, turning it back on again when the number of tasks falls below a lower limit (chosen to avoid constant stop-start) - that could then be a cron job (or equivalent) running (say) every 15 or 30 minutes. It won't solve the current problem but it would mean a recurrence could be avoided without the need for constant supervision! (I presume there isn't such a capability built into the generators already...)

That should be a main part of the boinc server software. Surely there's a setting to say what size each queue should be? Who writes this crap?