Brilliant….maybe someone will explain at least what changes were made to Nbody on or around 9th September.

State: All (353) · In progress (120) · Validation pending (0) · Validation inconclusive (170) · Valid (63) · Invalid (0) · Error (0)
Application: All (361) · Milkyway@home N-Body Simulation (353) · Milkyway@home Separation (8)

Thanks Tom, really appreciate the update info. Is the memory the type that we can help you with or is it "special" and only something we can contribute money for you to buy or is it even worth it, since you are talking about migrating to a new server anyway? It certainly will be nice when everything is updated and running smoothly again.
Thanks for your great efforts!!

Allen

The new server hardware has more than 2x the amount of memory as the current server, so once we migrate it should be less of a problem. The problem is migrating...!

Is it possible to track 2 items on a graph ..would be interesting to see Nbody average run time and total waiting for validation on the same graph. My own, probably misguided view is things have not been the same since we got these very long Nbody Simulation WU’s.

I have messed around with the graphs and going back 90 days there seems to be a massive spike in Nbody average run time that coincides with the growth of waiting for validation.Average Nbody run time is around 15 times higher than it used to be. I may be misguided in thinking the two are linked.

I guess its time to do daily postings of what the graph looks like for workunits and discussions(?):

5 Million waiting for validation by the end of tomorrow?

State: All (125) · In progress (91) · Validation pending (0) · Validation inconclusive (6) · Valid (28) · Invalid (0) · Error (0)
Application: All (133) · Milkyway@home N-Body Simulation (125) 

Putting this here so I'll remember what it is now: Workunits waiting for validation 3685233

Now it's 3678257 ...

[As it's too late to edit the previous post...]

Work downloading seems to have just started again :-). However, the number of work units waiting for validation is still climbing :-(.

I wonder how long it will be before it all bungs up again (or maybe even crashes [again?])

Cheers - Al.

I read the Adaptive Replication server documentation link from Kiska above and, I may be missing something, but it seems like Adaptive Replication is on for Separation but off for N-Body. Almost all of my Separation (GPU) tasks get validated without a second task but N-Body ones need a second one.