Advanced search

Message boards : Webpage and Application Code Discussion : Timed out tasks

Author Message
Capital Avionics
Send message
Joined: 16 Mar 15
Posts: 2
Combined Credit: 29,281,523
DNA@Home: 71,604
SubsetSum@Home: 534,285
Wildlife@Home: 28,675,634
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 5423 - Posted: 6 Jun 2015, 0:19:41 UTC

Two of my tasks missed their deadlines today. The reason for this is that one of those tasks has tied up that single-core machine for 85 hours and wants to run for 184 more hours (according to BOINC). The other task hasn't started yet. Should I abort them or let them run?

Profile Conan
Avatar
Send message
Joined: 13 Apr 12
Posts: 140
Combined Credit: 27,336,426
DNA@Home: 399,792
SubsetSum@Home: 1,448,876
Wildlife@Home: 25,487,758
Wildlife@Home Watched: 70,910s
Wildlife@Home Events: 0
Climate Tweets: 393
Images Observed: 0

          
Message 5425 - Posted: 6 Jun 2015, 3:02:56 UTC
Last modified: 6 Jun 2015, 3:03:26 UTC

The problem you are striking could be lack of memory for the DNA tasks. They often require at least 1 GB of memory and you only have between 700 and 800 MB in that computer.
This means that the computer is waiting for free resources to try and run the work unit, but can't as those resources just are not available.

Should run SubsetSum without too much of a problem through.

Conan
____________

Capital Avionics
Send message
Joined: 16 Mar 15
Posts: 2
Combined Credit: 29,281,523
DNA@Home: 71,604
SubsetSum@Home: 534,285
Wildlife@Home: 28,675,634
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 5426 - Posted: 6 Jun 2015, 3:34:43 UTC - in response to Message 5425.

The problem you are striking could be lack of memory for the DNA tasks. They often require at least 1 GB of memory and you only have between 700 and 800 MB in that computer. This means that the computer is waiting for free resources to try and run the work unit, but can't as those resources just are not available. Should run SubsetSum without too much of a problem through.


That could be the problem. I hope not because I couldn't find any more weirdo SIMMs that fit in those old slots. But that machine has done oodles of DNA tasks (slowly) without any problems. I'm not sure why the task history for that machine has been flushed.

Does this project have a deadline grace period? If so, I'll just let it play out.

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1793
Combined Credit: 2,265,607
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 1,622,832
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 710

              
Message 5432 - Posted: 6 Jun 2015, 23:42:43 UTC - in response to Message 5426.

The problem you are striking could be lack of memory for the DNA tasks. They often require at least 1 GB of memory and you only have between 700 and 800 MB in that computer. This means that the computer is waiting for free resources to try and run the work unit, but can't as those resources just are not available. Should run SubsetSum without too much of a problem through.


That could be the problem. I hope not because I couldn't find any more weirdo SIMMs that fit in those old slots. But that machine has done oodles of DNA tasks (slowly) without any problems. I'm not sure why the task history for that machine has been flushed.

Does this project have a deadline grace period? If so, I'll just let it play out.


The server flushes old workunits after a day or two, so that's probably why your task history is gone.


Post to thread

Message boards : Webpage and Application Code Discussion : Timed out tasks