WU Time estimates

Message boards : Number crunching : WU Time estimates

To post messages, you must log in.

AuthorMessage
neil.hunter14

Send message
Joined: 9 May 06
Posts: 10
Credit: 278,867
RAC: 0
Message 98392 - Posted: 31 Jul 2020, 9:37:11 UTC

Hi,
I have a query about the estimated time that my WU should be taking. On download, BOINC Manager states the WUs should last around 8 hours (Rosetta 4.20 - JHR_bd4 and bd5 models)
However, they have now been running for 13h 40m and still have over 11hrs to go. I'm now concerned they won't achieve the reporting deadline?
I've noticed this before.
How/why is the initial calculation so far out?

Regards,

Neil.
ID: 98392 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 1631
Credit: 16,728,284
RAC: 11,094
Message 98393 - Posted: 31 Jul 2020, 10:10:16 UTC - in response to Message 98392.  

How/why is the initial calculation so far out?
The default Target CPU time for processing Tasks is 8 hours and that is the initial Estimated completion time used- if you select a longer time, BOINC isn't aware of it. And it has been posted here that the estimates don't change from 8 hours these days for those that run with longer Target CPU time settings.

Some Tasks can take longer than the Target CPU time to process, and (if they haven't finished sooner) they will be ended 10 hours after the Target CPU time has been passed.
If your system is busy doing things other than processing BOINC work, it can take longer to process the Tasks than the Target CPU time. In some extreme cases, it can take a system over a day to do just 8 hours of work.
Another cause of extended times to process work is if people set "Use at most 100 % of CPU time" to anything less than 100%
Grant
Darwin NT
ID: 98393 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 1631
Credit: 16,728,284
RAC: 11,094
Message 98396 - Posted: 31 Jul 2020, 22:34:27 UTC
Last modified: 31 Jul 2020, 22:35:18 UTC

OK, you've completed some Tasks, and it shows that you have changed from using the default setting of 8 hours to 24hrs Target CPU time. Due to other system usage, actual processing time is around 25 hours.
Given that you are doing several projects, i'd suggest you set your cache to zero (if you haven't already done so).
In your computing preferences,
   Other	
                                Store at least 0    days of work
                     Store up to an additional 0.01 days of work
It reduces the problem of deadline issues due to differing deadlines between projects while the BOINC Manager sorts out processing times, and it allows your Resource share to settle down much sooner. And there's no need for a cache if you have more than one project anyway- the odds of all your projects not having work/being down at the same time are next to zero. If one goes down, the others will still keep your system crunching away.
Grant
Darwin NT
ID: 98396 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : WU Time estimates



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