WU time limiting - how works?

Message boards : Number crunching : WU time limiting - how works?

To post messages, you must log in.

AuthorMessage
Dave Mickey

Send message
Joined: 29 Dec 07
Posts: 33
Credit: 4,136,957
RAC: 0
Message 54169 - Posted: 4 Jul 2008, 16:39:20 UTC

I have a machine with 57.6K second runtime limt.
Recently had a WU go 117K seconds, while doing 11
decoys. I'm wondering how the limiting is done.

Did the WU do 10 of the decoys in less than 57K and
decide "OK, lets do one more" (which then took 60K
just for #11)?

Or, at WU start, does it decide "I think we can
squeeze out 11 decoys on this WU", and it just misjudged?

just curious

Dave
ID: 54169 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
transient
Avatar

Send message
Joined: 30 Sep 06
Posts: 376
Credit: 10,742,961
RAC: 3,369
Message 54171 - Posted: 4 Jul 2008, 17:13:29 UTC

As far as I know it works the first way.

Your computer did 10 decoys, and decided it could do one more, and still honor your 57.6K limit.
ID: 54171 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile sslickerson

Send message
Joined: 14 Oct 05
Posts: 101
Credit: 578,497
RAC: 0
Message 54173 - Posted: 4 Jul 2008, 18:16:46 UTC - in response to Message 54171.  

The WU in question is here

His runtime preference is 57600 seconds but the task finished at 117945 seconds, a full 16 more hours than required. For me, this means that the WU did complete 10 decoys before his runtime preference was achieved, however; the application thought it could do one more during the alloted time. It started and did not complete for at least 16 hours. It seems that something very wrong is going on here.



ID: 54173 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 54174 - Posted: 4 Jul 2008, 18:34:08 UTC - in response to Message 54169.  

Did the WU do 10 of the decoys in less than 57K and
decide "OK, lets do one more" (which then took 60K
just for #11)?


Yes, the best guess the program has, for how long the next model will take to process on your machine, is the time taken by the past models. However, each model is different then the others, and so it's actual runtime varies. For some recent tasks, it seems to occaisionally hit models that take extremely long times to complete. DK is looking in to the cause.

So I would say your description above that I quoted best describes what I believe occured.

Rosetta Moderator: Mod.Sense
ID: 54174 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : WU time limiting - how works?



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