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

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.

---

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