Opened 11 years ago
Last modified 11 years ago
#1321 new Enhancement
Avoid concurrent startup of tasks when the client is started
| Reported by: | Kevin Reed | Owned by: | davea |
|---|---|---|---|
| Priority: | Undetermined | Milestone: | Undetermined |
| Component: | Client - Scheduler Policy | Version: | 7.0.64 |
| Keywords: | Cc: |
Description
Some research projects use significant disk or other resources and concurrent start up of tasks can cause an impact on the system or possible result in heartbeat non-response. See http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,30688_offset,0#428458
It would be useful if the client would stagger the startup of tasks to avoid this issue or impact on the users machine.
Change History (2)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
What does BOINC report as the working set size of those jobs? How much RAM does the system have?
Note: See
TracTickets for help on using
tickets.
Would propose for the <start_delay> tag to also work when coming out of hibernation. Staggered starts would be ideal as a second control. Certainly have found that if 8 CEP2 start at the same time, there's at least an hour passing of disk trashing before even 1 second of CPU time is logged, if system is left alone. From user perspective impossible.