BOINC exceeded elapsed time limit


Advanced search

Message boards : Client : BOINC exceeded elapsed time limit

Author Message
LordOfWar
Send message
Joined: 3 Jun 08
Posts: 9
Credit: 435,513
RAC: 0
Message 11068 - Posted: 2 Nov 2011, 6:45:05 UTC

Copied from event log:

11/2/2011 1:25:34 AM | BURP | Aborting task ses0000001279frm0000000029prt00001_2: exceeded elapsed time limit 50019.37 (800000.00G/15.99G)

This is the page for the task: http://burp.renderfarming.net/result.php?resultid=6952017

This is not the first event log I have gotten like this for session 1279. I have failed at least 4 work units for this session.

I see other people taking much more time than me for tasks in this session, let me use frame 2 as an example.

Here it shows that 126,373.13s was the highest run time, but their task wasn't aborted. Their computer is http://burp.renderfarming.net/show_host_detail.php?hostid=48857.

Another computer for this work unit stopped after 30,397.00s with what appears to be the same reason mine aborted.

My Computer (id 52250)

At first I thought maybe it was the boinc version having a new feature, but I have the same version of boinc as the computer with the 126,373.13s run time.

Maybe BOINC over-values my computer's computational abililty? A lot of tasks could be being aborted because boinc shuts it down for taking too long, when really there is no problem. If my assumption is correct, maybe the estimated task size needs to be increased (add a higher multiplier for buffer range maybe?).

Is there a way to turn this BOINC feature off?

Let me know what you think.

Thanks!

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 11070 - Posted: 3 Nov 2011, 7:43:16 UTC

You are quite right, good catch! It is a little complicated but BOINC does indeed seem to treat the time limit incorrectly.

LordOfWar
Send message
Joined: 3 Jun 08
Posts: 9
Credit: 435,513
RAC: 0
Message 11075 - Posted: 3 Nov 2011, 17:29:39 UTC - in response to Message 11070.

Can you post back here when that is fixed (or the fpops limit for session 1279 is increased (maybe 3 times current amount or more?)), until then I'll have to babysit my BOINC client and abort tasks from session 1279.

Thanks!

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 11077 - Posted: 3 Nov 2011, 18:17:15 UTC

The fix has been deployed but it may take a little while before the old workunits have been removed from the queue.


Post to thread

Message boards : Client : BOINC exceeded elapsed time limit