About four days ago, Boinc (latest) has been running a little bizarre with Einstein@Home, I run SETI and Milky as well and they are both fine.
I find Einstein will not stop jumping around on which Work Units it should do, it will do one for 80% then jump to a next one for 15% then another at 30% then another one at 99%, and they are completely random on when they start on stop. Right now I have it switching between Projects every 12 hours, and when I look at Einstein it has started about 15 Work Units and finished 0, and now I have some deadlines coming up tomorrow so now I have to stop the other projects to finish these WUs.
Any idea to why it started?
Copyright © 2024 Einstein@Home. All rights reserved.
Einstein Help
)
Your host (2322029) seems to be running a development version of BOINC - v6.10.29 - but by no means the latest: there's been a v6.10.32 and a v6.10.34 since then.
There have been sporadic reports on this message board of hosts ending up with far more work than they can comfortably deal with before the deadline: nobody has posted any logging records to demonstrate whether the hosts request too much work - which might be a BOINC client problem - or are allocated excess work - which could indicate a server problem. I have seen the problem myself (once, on one machine), but stupidly didn't have enough logging enabled to help solve the mystery.
(Co-incidentally, that excess workload will finally be cleared in about 7 minutes from now. I might try again!)
Well... I have
)
Well... I have approximately... 37 WU Einstein@Home due by March 3rd. I thought this was normal and it was basing it off the CPU / GPU benchmarks of my laptop. I will update boinc, thanks for pointing that out.
Richard: Looking at my i7
)
Richard: Looking at my i7 host I see that the needed DCFs for regular and ABP work units are way off. Normal WU's. The normal WU's are at 5-6hrs which is about right; the ABPs are showing about 9. My machine crunches the 160 credit ABP WU's in about 3 hours. Wild swings in DCF depending on what type of work is being primarily crunched could result in a host getting overloaded. I've seen this host have a few days more work than it should have, but until now hadn't realized what was likely to blame.