The title says it all ....

Could try the Nbody Simulation, credits are poor but they don’t take very long.

Thanks, I know, but I'm GPU only on MW ...

Ok fair enough…happy crunching.

Yeah, it's a little goofy. I'm back to having to do update requests in the hopes of getting some work units every once in a while, when I can. Also now there seems to be one stuck in "in progress" for a couple days that isn't on my computer anywhere that I can tell, even after resetting the project, certainly not running. https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=417189391

Funny enough though, my average credit rates still seem to be going up (for now) since setting my computer up to work on MW@H again, and since then now there are enough work units still in "validation pending" and "validation inconclusive" that when they are validated it's still at a faster credit rate even though my computer is often idle in terms of MW@H GPU work units.

---

Everybody has some "ghost" tasks from around March 20 that were assigned to their hosts but never delivered. Nothing wrong with your hosts or anything you can do about it since it was a server hiccup out of your control.

They should eventually disappear from your lists. But could be permanent as the situation back in January 2021 where the database was scrambled and tasks were orphaned.

---

Could try the Nbody Simulation, credits are poor but they don’t take very long.

Are the credits poor because it computes credits based on elapsed time and not CPU time?

It's been such a long time since I did any N-body that I can't remember how it awards credit. Elapsed compute time should not matter.

I thought it was fixed as in the Separation tasks but someone will correct me if I am wrong.

---

I recall some time ago there was talk of stopping tasks from "Separation v1.46" running on the CPU as these are 1 task per core, did I get my wires crossed?

Yeah, it's one task per core. But sure hope they won't be stopped, since it seems to be all I can process, or at least never received N-Body, maybe because I do CPU only and it's an old one and 32-bit OS (4 GB RAM and no dedicated video card, so 64-bit would just increase RAM use for no benefit).

What's up with the server? There's no Separation work ready to send.

What's up with the server? There's no Separation work ready to send.

If you look at the status page you'll notice there is a huge backlog of tasks awaiting validation. The bulk of these are likely to be Separation tasks (as the daily turnover of N-Body tasks is in the low to mid 300,000s but the backlog built up to over 1.5 million in a couple of days!) There is also a very large transitioner backlog at present.

As I understand it, the construction of new work units (after those that initialize the batch) depends to some extent on results already returned, validated and assimilated -- if that is the case, it is possible that there are so many results not yet finalized that the only tasks available will be retries, and retry set-ups will take ages to work through the system at present, with that huge transitioner backlog!

I suspect Tom will need to take the server offline to clear the transitioner backlog, which may or may not help -- as an end user I can't tell whether the validators are busy or are not getting enough requests from the transitioner at present...

Cheers - Al.

P.S. I suspect the return of users from Einstein and other projects as the recent challenge wound down hasn't helped.

What's up with the server? There's no Separation work ready to send.

I think they heard you: Milkyway@home Separation Unsent 835645 In progress 1025531