Application freezing on 1,000%

Questions and Answers : Preferences : Application freezing on 1,000%

To post messages, you must log in.

AuthorMessage
Novasen169

Send message
Joined: 26 Oct 06
Posts: 2
Credit: 160,850
RAC: 0
Message 30224 - Posted: 29 Oct 2006, 13:59:10 UTC
Last modified: 29 Oct 2006, 14:01:14 UTC

Hi,

I've only attached to R@H recently and in the 4/5 workunits I've done 3 froze on exactly 1,000%. It kept using CPU Time, but it didn't progress in %, nor did the graphics show anything.
So after it used about an hour of CPU time without any progress I decided to just abort them.
Those are the results I'm talking about:
https://boinc.bakerlab.org/rosetta/result.php?resultid=44226912
https://boinc.bakerlab.org/rosetta/result.php?resultid=44072040
https://boinc.bakerlab.org/rosetta/result.php?resultid=44226913

I checked the workunits and on the oldest one it was resent and the other person got a compute error as well.

What's up with this?

EDIT: I only just found the answer in the FAQ, sorry for asking it here.
ID: 30224 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Christoph Jansen
Avatar

Send message
Joined: 6 Jun 06
Posts: 248
Credit: 267,153
RAC: 0
Message 30238 - Posted: 29 Oct 2006, 19:04:49 UTC

Salve Seneca,

your WUs are all very computationally intensive ones that have caused problems on other machines because the yielded extremely low credits, meaning the took a lot of time to crunch the first decoy. So it is very probable that your machine did not crunc a single decoy in the time you watched it.

That is why the WUs were still at 1%, which is the default before any real progress has been made. Still, the CPU time keeps ticking down as you watch it and gives you the impression of no progress at all.

So just forget these, they were taken out of the pipeline until the staff understand what went wrong (at least that is what I understood frome the thread "Low scores anyone?" in the Number Crunching Forum.

Regards,

Christoph
ID: 30238 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Novasen169

Send message
Joined: 26 Oct 06
Posts: 2
Credit: 160,850
RAC: 0
Message 30261 - Posted: 30 Oct 2006, 0:50:46 UTC - in response to Message 30238.  

Salve Seneca,

your WUs are all very computationally intensive ones that have caused problems on other machines because the yielded extremely low credits, meaning the took a lot of time to crunch the first decoy. So it is very probable that your machine did not crunc a single decoy in the time you watched it.

That is why the WUs were still at 1%, which is the default before any real progress has been made. Still, the CPU time keeps ticking down as you watch it and gives you the impression of no progress at all.

So just forget these, they were taken out of the pipeline until the staff understand what went wrong (at least that is what I understood frome the thread "Low scores anyone?" in the Number Crunching Forum.

Regards,

Christoph


Thanks for your reply.. Well I doubt they did, I think my 3,2 GHz Pentium IV should do that in less than one hour..

By the way, is the problem with the low credit claims solved.. the thread ended without a solution.. Are they supposed not to be distributed anymore?

ID: 30261 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Questions and Answers : Preferences : Application freezing on 1,000%



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