die erste Adresse für Distributed Computing
Unterstütze Rechenkraft.net e.V. |
Mit Suchkraft hier suchen:
fractal wrote:I read the thread that says a 2 GHz athlon will finish all work in a couple of hours. If this is true then shouldn't the work automatically abort after a day and not tie up a core for a week when you guys give us buggy work?
fractal wrote:I was referring to viewtopic.php?f=75&t=10592 . Re-reading it I see you said 47 hrs on a 2ghz AMD.
fractal wrote:It is currently at 145 hrs of processing and time to complete has fluctuated between 10 and 12 hrs for the past two days. Report deadline is 5 hrs from now. You might want to take a look at that unit since, as I reported earlier, nobody has finished it and 64 bit linux cores that could be used to clean up the backlog of pending are tied up on it.
FalconFly wrote:I also have two WorkUnits ( example ) that could not finish within the deadline.
Both take approx. 670hrs on a 2.5GHz Phenom II X4 905e, which isn't quite a slow CPU.
x86_64 Linux reports normal CPU usage, Task is running normal.
As the deadline is already blown, should I abort those or should I wait another ~340hrs for them to complete ?
(i.e. will the server still accept them ?)
-- edit --
Restarting them seems to have resetted their figures. I guess I'll keep an eye on how they proceed (?)
total used free shared buffers cached
Mem: 4038988 3770556 268432 0 109184 357996
-/+ buffers/cache: 3303376 735612
Swap: 1253028 916248 336780
Al Dente wrote:And another very long unit (513689, cms_6S6[e]_Monodelphis-domestica-(gray-short-tailed-opossum)_CM000370.lin.EMBL_f_1268060823_33_0), running on a Q6600/2.4GHz, but only 2GB RAM.
It's currently at 63¾ hours @ 9.1%, so ~637 hours/26½ days to go at the current rate; the progress bar is clicking up 0.001% per tick. The deadline is 18/3 (just under 7 days); it's showing 125 hours to go, so BOINC hasn't put it on high priority yet.
Abort (I hate wasting crunching time) or persevere?
Users browsing this forum: Yahoo [Bot] and 5 guests