making the deadline...

Questions and Answers : Macintosh : making the deadline...

To post messages, you must log in.

AuthorMessage
Profile Om
Avatar

Send message
Joined: 18 Feb 20
Posts: 16
Credit: 777,076
RAC: 0
Message 91908 - Posted: 10 Mar 2020, 0:59:56 UTC

The way it looks, I'm going to have a bunch of WU's that won't make the deadline. I originally set it up for 3 days of work, which has since been changed to 1 day of work. Will BOINC be able to sort this out, or will I have to abort the WU's that won't make the deadline?
Any insight would be appreciated!
ID: 91908 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4016
Credit: 0
RAC: 0
Message 91916 - Posted: 10 Mar 2020, 15:45:14 UTC

The BOINC Manager will sort it out, but you may prefer to do it yourself.

I would first mark R@h for no new work, then go ahead and "abort" any WUs that have not yet begun processing. Then perhaps adjust the preference for how many days of work you want to download. Then allow new work for the project again.

The BOINC Manager will get a better understanding of the processing time as it completes the first few, and should be more accurate in the future on matching the work requests to the request size of your cache of work.
Rosetta Moderator: Mod.Sense
ID: 91916 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
D J Blumer

Send message
Joined: 6 Nov 05
Posts: 3
Credit: 29,259,406
RAC: 41,671
Message 94475 - Posted: 14 Apr 2020, 21:12:24 UTC

Has the deadline for workunits been decreased lately? I now am getting ones with deadlines within 1- 2 days of when I receive them. I noticed that some are not completing in time anymore, which seldom, if ever, happened in all the many years I've run R@h. I have shortened the downloaded days of work to 1 day from the 2 days I had until now. I hope that solves the problem. I wasted quite a bit of computer time on results that were declared invalid due to missing the deadline.
ID: 94475 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4016
Credit: 0
RAC: 0
Message 94484 - Posted: 14 Apr 2020, 22:56:24 UTC

The project has always had a mix of 7+ day deadlines and 3 day deadlines.

There have been some batches of WUs failing very quickly. This caused some folks' BOINC Manager to request too many WUs. By that, I mean that if they had a WU cache of 2 days, like you, they might actually get 5 or 7 days worth of work (which then had 3 day deadlines).

Reducing your cache size as you described is ideal. The BOINC Manager will realign itself as it sees successful completed WUs.
Rosetta Moderator: Mod.Sense
ID: 94484 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 750
Credit: 5,132,124
RAC: 21,415
Message 94489 - Posted: 14 Apr 2020, 23:32:28 UTC - in response to Message 94475.  

I have shortened the downloaded days of work to 1 day from the 2 days I had until now. I hope that solves the problem. I wasted quite a bit of computer time on results that were declared invalid due to missing the deadline.
If you only run Rosetta, then
                                Store at least 1 days of work
                     Store up to an additional 0.02 days of work
works well. More than one project, then "Store at least 0.5 days of work" (or less) would be better.
Grant
Darwin NT
ID: 94489 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Nicholas Hathaway

Send message
Joined: 20 Nov 14
Posts: 6
Credit: 791,395
RAC: 136
Message 94501 - Posted: 15 Apr 2020, 1:25:22 UTC - in response to Message 91908.  

The way it looks, I'm going to have a bunch of WU's that won't make the deadline. I originally set it up for 3 days of work, which has since been changed to 1 day of work. Will BOINC be able to sort this out, or will I have to abort the WU's that won't make the deadline?
Any insight would be appreciated!



I have the same problem. I have Was that say they will take 5 hours or so to run, but they are still running after 17 hours, and some now display that will take another day and a half. Indeed, they seem to increase their estimated run time! Do I have a problem or is this normal?
ID: 94501 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Nicholas Hathaway

Send message
Joined: 20 Nov 14
Posts: 6
Credit: 791,395
RAC: 136
Message 94502 - Posted: 15 Apr 2020, 1:33:53 UTC

My work units arrive and they say that they will take 5 hours or so to complete, however, not only are they still running some 17 hours later but they all seem to increase the estimated computing time, I have some showing 1 day and 15 hours left! None of them are going to make the deadline of today. Is there an error somewhere, is it me, is this normal?
ID: 94502 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 750
Credit: 5,132,124
RAC: 21,415
Message 94503 - Posted: 15 Apr 2020, 2:09:31 UTC - in response to Message 94502.  

My work units arrive and they say that they will take 5 hours or so to complete, however, not only are they still running some 17 hours later but they all seem to increase the estimated computing time, I have some showing 1 day and 15 hours left! None of them are going to make the deadline of today. Is there an error somewhere, is it me, is this normal?
The default Runtime is 8 hours. Have you changed this setting in the Roesetta account, Rosetta@ home preferences? It should be,
Target CPU run time not selected
to use the default of 8 hours.


What are your settings under Computing preferences? How do they differ from these settings?
Computing
   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 ---

   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

   Disk
                              Use no more than 20 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 %
Anything that suspends work will result in things taking much longer to finish (though the CPU time & Runtime will still be whatever you have selected, but there is a 3 day deadline so a Task needs to finish before then.

And on one of your Tasks it shows the CPU is doing things other than processing BOINC work, as well & stopping & starting work several times.
Run time	17 hours  5 min 4 sec
CPU time	15 hours 28 min 36 sec
Over 16 hours, the difference between CPU time & Runtime shouldn't be much more than 5min or so unless the system is doing a lot of other things, or you have "Use at most 100% of CPU time" set to less than 100%.
Grant
Darwin NT
ID: 94503 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Tom Coradeschi

Send message
Joined: 11 Mar 20
Posts: 10
Credit: 105,271
RAC: 0
Message 94505 - Posted: 15 Apr 2020, 3:54:46 UTC - in response to Message 94503.  

My work units arrive and they say that they will take 5 hours or so to complete, however, not only are they still running some 17 hours later but they all seem to increase the estimated computing time, I have some showing 1 day and 15 hours left! None of them are going to make the deadline of today. Is there an error somewhere, is it me, is this normal?
The default Runtime is 8 hours. Have you changed this setting in the Roesetta account, Rosetta@ home preferences? It should be,
Target CPU run time not selected
to use the default of 8 hours.


Umm, I'm totally missing where you find this setting. Can you help me figure it out?
ID: 94505 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Tom Coradeschi

Send message
Joined: 11 Mar 20
Posts: 10
Credit: 105,271
RAC: 0
Message 94506 - Posted: 15 Apr 2020, 3:56:30 UTC - in response to Message 94505.  

My work units arrive and they say that they will take 5 hours or so to complete, however, not only are they still running some 17 hours later but they all seem to increase the estimated computing time, I have some showing 1 day and 15 hours left! None of them are going to make the deadline of today. Is there an error somewhere, is it me, is this normal?
The default Runtime is 8 hours. Have you changed this setting in the Roesetta account, Rosetta@ home preferences? It should be,
Target CPU run time not selected
to use the default of 8 hours.


Umm, I'm totally missing where you find this setting. Can you help me figure it out?


Ah. It's a server side setting?
ID: 94506 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 750
Credit: 5,132,124
RAC: 21,415
Message 94507 - Posted: 15 Apr 2020, 4:57:33 UTC - in response to Message 94506.  
Last modified: 15 Apr 2020, 4:58:45 UTC

Umm, I'm totally missing where you find this setting. Can you help me figure it out?
Ah. It's a server side setting?
On the top of this page, click on your name, that will take you to your account, then under Preferences, Preferences for this project- Rosetta@home preferences. Click on that, then the Edit preferences near the bottom & you can select the Target CPU Runtime, or select "Not selected" to use the project default. Then click on Update preferences to save the changes.
The next time the Manager contacts Rosetta it will get the new settings, or if you have Rosetta selected and manually select Update it will get them then.


I have had 2 Tasks run longer than the Target CPU time so far today, but they've been the only ones i've come across in the last few weeks.


NB- any locally set preferences will override any web based preferences.
Grant
Darwin NT
ID: 94507 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Nicholas Hathaway

Send message
Joined: 20 Nov 14
Posts: 6
Credit: 791,395
RAC: 136
Message 94646 - Posted: 17 Apr 2020, 1:26:53 UTC - in response to Message 94503.  

My work units arrive and they say that they will take 5 hours or so to complete, however, not only are they still running some 17 hours later but they all seem to increase the estimated computing time, I have some showing 1 day and 15 hours left! None of them are going to make the deadline of today. Is there an error somewhere, is it me, is this normal?
The default Runtime is 8 hours. Have you changed this setting in the Roesetta account, Rosetta@ home preferences? It should be,
Target CPU run time not selected
to use the default of 8 hours.


What are your settings under Computing preferences? How do they differ from these settings?
Computing
   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 ---

   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

   Disk
                              Use no more than 20 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 %
Anything that suspends work will result in things taking much longer to finish (though the CPU time & Runtime will still be whatever you have selected, but there is a 3 day deadline so a Task needs to finish before then.

And on one of your Tasks it shows the CPU is doing things other than processing BOINC work, as well & stopping & starting work several times.
Run time	17 hours  5 min 4 sec
CPU time	15 hours 28 min 36 sec
Over 16 hours, the difference between CPU time & Runtime shouldn't be much more than 5min or so unless the system is doing a lot of other things, or you have "Use at most 100% of CPU time" set to less than 100%.
ID: 94646 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Nicholas Hathaway

Send message
Joined: 20 Nov 14
Posts: 6
Credit: 791,395
RAC: 136
Message 94647 - Posted: 17 Apr 2020, 1:27:46 UTC - in response to Message 94646.  

In the end I 'reset' the project by means of the 'Reset' button, and it is working normally now. Thank you.
ID: 94647 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
sangham
Avatar

Send message
Joined: 19 Mar 20
Posts: 4
Credit: 26,251
RAC: 0
Message 95387 - Posted: 26 Apr 2020, 5:35:34 UTC - in response to Message 94484.  

Hello,
I ran exactly into the same problem as DJ Blume. How can I adjust the settings to 1 Day workload? Unfortunately I cannot afford wasting that much computation time.

Thank you.
ID: 95387 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
sangham
Avatar

Send message
Joined: 19 Mar 20
Posts: 4
Credit: 26,251
RAC: 0
Message 95388 - Posted: 26 Apr 2020, 5:48:45 UTC - in response to Message 95387.  

ok, if it's this here, I found it:

Store at least 1 days of work
Store up to an additional 0.02 days of work

(that was 0,1 days of work and 0,5 in addition before).

I changed to settings quoted above - is that what you meant by ideal solution?
ID: 95388 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 750
Credit: 5,132,124
RAC: 21,415
Message 95389 - Posted: 26 Apr 2020, 6:41:04 UTC - in response to Message 95388.  

Store at least 1 days of work
Store up to an additional 0.02 days of work
(that was 0,1 days of work and 0,5 in addition before).

I changed to settings quoted above - is that what you meant by ideal solution?
0,4 days of work and 0,02 additional days would be better choices if you want to carry around half a days days worth of work.
One of the issues is that the Estimated completion times tend to be a fair bit less than reality, so people und up with more work than they want (and often more work than they can possibly do).
And if your system spends a lot of time doing things other than just Rosetta, then the time it takes to actually do a Task is longer than the Target Time. So a very small cache (0.5 days, or even next to no cache; eg 0.2) is best.

Give it a week or so to see how things are going & then adjust things further if necessary.
Grant
Darwin NT
ID: 95389 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
sangham
Avatar

Send message
Joined: 19 Mar 20
Posts: 4
Credit: 26,251
RAC: 0
Message 95397 - Posted: 26 Apr 2020, 14:22:45 UTC - in response to Message 95389.  

ok, thank you Grant
ID: 95397 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Questions and Answers : Macintosh : making the deadline...



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