Uncertainty about the timeout being enforced comes from the fact that the Performance page will list several batches with maximum run time (in the box-plots) of well over 120 hours.

In the past couple of weeks, the lion's share of WUs have been running very, very long.
In the past week or so, I have aborted a dozen or more WUs because, while running, they were heading to well over 5 days of compute time.
At this posting I have a WU running with anticipated completion time of just over 11 days (270 hours). I really would like to run this one, since I have not been able to run any GPUGRID WUs in nearly two weeks.

Thanks.
LLP, PhD PE

PS I asked this question on the BNBS thread as part of a post there, but I think the question if pretty important overall for GPUGRID

keywords: Timed out, limit

---

I think ∴ I THINK I am
My thinking neither is the source of my being
NOR proves it to you
God Is Love, Jesus proves it! ∴ we are

Yes, after 5 days the WU is resent and classed as "Timed Out" however, if you return the result before the second host does you still get credit no matter how long it takes.

A surprisingly large number of hosts steal WUs and keep them for the full 5 days and do this continuously. Due to the nature of these work flows they are in chains and the results of one WU lead to another. If someone has a WU no one else can have it until they are either done with it, error out, or wait 5 days. Increasing this would slow down everything, so my advice to you is to buy a cheap gtx 1050 or 1050ti with no extra power supply requirements.

buy a cheap gtx 1050 or 1050ti with no extra power supply requirements

Right, I second that.

---

I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.