1.030% after 6 hours crunching?

Author	Message
Walter Kraslawsky Send message Joined: 19 May 06 Posts: 3 Credit: 41,392 RAC: 0	Message 17810 - Posted: 6 Jun 2006, 17:08:21 UTC Last modified: 6 Jun 2006, 17:36:26 UTC I don't mind crunching a long task as long as it isn't wasted effort. But one of my computers has a task (https://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 Charity begins @Home... SETI Classic: 06 June 2002 / 51 WU / 2,554 Hours ID: 17810 · Rating: 0 · rate: / Reply Quote

Walter Kraslawsky Send message Joined: 19 May 06 Posts: 3 Credit: 41,392 RAC: 0	Message 17838 - Posted: 6 Jun 2006, 19:48:18 UTC Last modified: 6 Jun 2006, 19:53:27 UTC 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 Charity begins @Home... SETI Classic: 06 June 2002 / 51 WU / 2,554 Hours ID: 17838 · Rating: 1 · rate: / Reply Quote

Feet1st Send message Joined: 30 Dec 05 Posts: 1755 Credit: 4,690,520 RAC: 0	Message 18019 - Posted: 7 Jun 2006, 22:27:53 UTC - in response to Message 17838. 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. Add this signature to your EMail: Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might! https://boinc.bakerlab.org/rosetta/ ID: 18019 · Rating: 1 · rate: / Reply Quote

Walter Kraslawsky Send message Joined: 19 May 06 Posts: 3 Credit: 41,392 RAC: 0	Message 18068 - Posted: 8 Jun 2006, 5:11:30 UTC - in response to Message 18019. 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 Charity begins @Home... SETI Classic: 06 June 2002 / 51 WU / 2,554 Hours ID: 18068 · Rating: -1 · rate: / Reply Quote