Work aborted due to not starting before deadline

Message boards : Number crunching : Work aborted due to not starting before deadline

To post messages, you must log in.

AuthorMessage
Steve MacKenzie

Send message
Joined: 28 Mar 09
Posts: 1
Credit: 45,989
RAC: 0
Message 94133 - Posted: 11 Apr 2020, 3:16:54 UTC

As the title suggests. About half of my work is aborting for this.
The estimated times to completion are around 1/2 the actual times to complete.
Anything I can do to fix this ?
I'm an old legacy (2000) SETI user and never ran into this over there.
Thanks in advance
Steve
ID: 94133 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 1681
Credit: 17,854,150
RAC: 22,647
Message 94134 - Posted: 11 Apr 2020, 3:32:34 UTC - in response to Message 94133.  
Last modified: 11 Apr 2020, 3:34:44 UTC

As the title suggests. About half of my work is aborting for this.
The estimated times to completion are around 1/2 the actual times to complete.
Anything I can do to fix this ?
It's the same as with Seti and a new application- it takes time for the Estimated completion times to match reality. The default Target CPU runtime is 8 hours, and so it does take even longer for the Estimated times to match reality.

If you set a small cache-
your Account, Computing preferences,
   Other	
                                Store at least 1 days of work
                     Store up to an additional 0.02 days of work
                    Switch between tasks every 60 minutes
     Request tasks to checkpoint at most every 60 seconds
that will help to stop it from occurring in the future.
Once the BOINC Manager has contacted the Scheduler & got those new settings, you can abort any older Tasks yet to be run to avoid having them cancelled after you've spent time processing them. The new cache setting will let you get new work, but not more than you can do before the deadline is reached.
And once the Estimated completion times settle down it will allow you enough work to meet the cache settings.


Moving from Seti, there are a few other things you might want to change to avoid problems in the future, the present Tasks don't use much RAM or HDD space, but many of the usual Tasks use way, way, way more.
Roughly 1.3GB RAM and 1GB HDD space per Task (most are smaller than that, but there are some that size). Allow for those amounts & you shouldn't have any future issues.
*fingers crossed*




   Usage limits	
                                   Use at most 100% of the CPUs
                                   Use at most 100% of CPU time

   When to suspend	
           Suspend when computer is on battery (not selected)
               Suspend when computer is in use (not selected)
 Suspend GPU computing when computer is in use (not selected)
   'In use' means mouse/keyboard input in last 3 minutes
  Suspend when no mouse/keyboard input in last --- minutes
     Suspend when non-BOINC CPU usage is above --- %
                          Compute only between ---




   Disk
                              Use no more than 4.5 GB
                                Leave at least 2 GB free
                              Use no more than 60 % of total

   Memory
          When computer is in use, use at most 95 %
      When computer is not in use, use at most 95 %
 Leave non-GPU tasks in memory while suspended (not selected)
                   Page/swap file: use at most 75 %

Grant
Darwin NT
ID: 94134 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : Work aborted due to not starting before deadline



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