Okay, I got one. But, I got it on an old P-IV era Xeon machine that has hyperthreading enabled. Right now, I'm seven hours and 11 minutes into it, and have just now gone over 10% completion. So, with only a three-day deadline, I'll be cutting it close.
Hallo BM!
Are these new apps running for test with high priority? I hope so.
Kind regards and happy crunching
Martin
That's not something the project can control. 'High Priority' is set by your local client if it needs to gueue-jump the task in order to meet the deadline.
Hallo BM!
Are these new apps running for test with high priority? I hope so.
Kind regards and happy crunching
Martin
That's not something the project can control. 'High Priority' is set by your local client if it needs to gueue-jump the task in order to meet the deadline.
... if it thinks it needs to ...
I'm sure this behaviour has intentionally been "encouraged" by the short deadline and it will likely change after the test phase. But then there's still the estimated run time which is currently vastly overestimated. The WUs seem to consist of several parts, each starting at 0% and running to an unpredictable percentage. I think this will make it hard to get reliable estimates.
This workunit is showing very strange behavior. It keeps advancing to a certain percentage done, and then the Progress counter keeps getting reset to zero, and it starts over. Right now, after over 21 hours, it's showing at about 13% completion, with 240 hours left to go. My computer is number 6345035.
Gravitational Wave search S6Bucket Follow-up #1 launched
)
Don't know if this is directly related to this new release, but i hat a few bad gateway messages from boinc, but for the first time this:
http://einstein.phys.uwm.edu/host_sched_logs/2380/2380567
btw, no forced update at this time
edit:
oh, was only a small hiccup:
from my POV, all is well again
11/20/2014 1:49:09 PM |
)
11/20/2014 1:49:09 PM | Einstein@Home | No work is available for Gravitational Wave search S6Bucket Follow-up #1
None for me.
Okay, I got one. But, I got
)
Okay, I got one. But, I got it on an old P-IV era Xeon machine that has hyperthreading enabled. Right now, I'm seven hours and 11 minutes into it, and have just now gone over 10% completion. So, with only a three-day deadline, I'll be cutting it close.
Hallo BM! Are these new apps
)
Hallo BM!
Are these new apps running for test with high priority? I hope so.
Kind regards and happy crunching
Martin
RE: Hallo BM! Are these new
)
That's not something the project can control. 'High Priority' is set by your local client if it needs to gueue-jump the task in order to meet the deadline.
RE: RE: Hallo BM! Are
)
... if it thinks it needs to ...
I'm sure this behaviour has intentionally been "encouraged" by the short deadline and it will likely change after the test phase. But then there's still the estimated run time which is currently vastly overestimated. The WUs seem to consist of several parts, each starting at 0% and running to an unpredictable percentage. I think this will make it hard to get reliable estimates.
This workunit is showing very
)
This workunit is showing very strange behavior. It keeps advancing to a certain percentage done, and then the Progress counter keeps getting reset to zero, and it starts over. Right now, after over 21 hours, it's showing at about 13% completion, with 240 hours left to go. My computer is number 6345035.
Strange workunit
Thanks. There might (still)
)
Thanks. There might (still) be something wrong with the progress accounting. However the calculation usually works as it should.
BM
BM
RE: Thanks. There might
)
Well, it seems to be doing better now. At 23 hours, 29 minutes, it's showing as 75.25% complete, with 12 hours 48 minutes to go.
RE: RE: Thanks. There
)
I spoke too soon. It reset itself again, and is now showing at about 8% and 277 hours left to go.