Posts by Walter Kraslawsky

1) Questions and Answers : Web site : 1.030% after 6 hours crunching? (Message 18068)
Posted 8 Jun 2006 by Profile Walter Kraslawsky
Post:
Does Rosetta use the previous task CPU Time to estimate the run time of the next task?


Yep! It's actually a BOINC trait.

I'm trying to describe this in a Q&A thread. Drop a question there if you don't find the descriptions clear enough.


Hmmm... I expected the Q&A thread to expand on the run time estimate explanation, since that is the part of my message that you quoted. It didn't, but it did very nicely explain the more difficult original problem with appearing to be stuck on 1.030%. Many thanks.

V/R,
Walt
2) Questions and Answers : Web site : 1.030% after 6 hours crunching? (Message 17838)
Posted 6 Jun 2006 by Profile Walter Kraslawsky
Post:
uh ... Never mind. I just looked at it again, and it is now "Ready to Report" at 100% after CPU Time 06:51:54.

I guess there is a bug in how Rosetta calculates progress percent and time to completion. That is a separate issue that is worth investigating by the Rosetta developers.


What is also VERY interesting is that the next Rosetta task, which is at 0.000% "Ready to Run," shows To Completion of 06:51:54. This couldn't be a coincidence. Does Rosetta use the previous task CPU Time to estimate the run time of the next task?

V/R,
Walt
3) Questions and Answers : Web site : 1.030% after 6 hours crunching? (Message 17810)
Posted 6 Jun 2006 by Profile Walter Kraslawsky
Post:
I don't mind crunching a long task as long as it isn't wasted effort. But one of my computers has a task (http://boinc.bakerlab.org/rosetta/result.php?resultid=22808132) that cannot possibly meet the report deadline if the Progress stat is correct:

CPU Time: 06:23:06
Progress: 1.030%
To Completion: 09:25:08PM

When I watch it running, both CPU Time and time to completion increase (continuously recalculating new completion time), but progress percent remains a hair over 1%.

Please advise. If this is a corrupted task, I'd rather suspend it and give the CPU time to something else.

V/R,
Walt






©2025 University of Washington
https://www.bakerlab.org