| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: Limit task run length |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
ElrondPA
Cruncher Joined: Apr 27, 2007 Post Count: 10 Status: Offline Project Badges: 
|
I have BOINC installed on several computers. One of them is turned on for shorter periods (normally not more than 3-4 hours a day; sometimes a few days will go by with no usage at all). I'm noticing that sometimes a long-running task gets assigned, and it's hard to give it enough time to run before the task's report deadline. Right now, it's running a job estimated to take 14 hours; a second job on the dual-core machine is estimated to take 6.
It would be helpful to have a Device Manager setting that would limit the device to downloading tasks expected to take a specified maximum number of hours. This would, I think, be particularly useful for laptops, which often are running (on AC power) only a small part of the day. Since they often have less powerful CPUs (to reduce power consumption), jobs run longer on them to begin with. |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2955 Status: Offline Project Badges: 
|
As a quick fix, I'd suggest running HCC only on that machine which isn't on for long periods - as these WU's are generally very short.
----------------------------------------Edit: After checking the WCG Supplemental Performance Charts - 1 it can be seen that, in the first chart, the current averages for each of the WU's/project are shown; Hours/Task Thus, after HCC, HCMD2 followed by C4CW is best.  [Edit 1 times, last edit by gb009761 at May 31, 2011 4:05:09 PM] |
||
|
|
ElrondPA
Cruncher Joined: Apr 27, 2007 Post Count: 10 Status: Offline Project Badges:
|
Thanks for the suggestion. I've set up a new device profile to put this into effect.
----------------------------------------The suggestion for future enhancement still stands, though, since I still don't have control over maximum length. [Edit 1 times, last edit by ElrondPA at Jun 23, 2011 4:43:31 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As a quick fix, I'd suggest running HCC only on that machine which isn't on for long periods - as these WU's are generally very short. Edit: After checking the WCG Supplemental Performance Charts - 1 it can be seen that, in the first chart, the current averages for each of the WU's/project are shown; Hours/Task Thus, after HCC, HCMD2 followed by C4CW is best. In the process of changing the Min/Max day task hourly averages from All-Time to last 6 months, to give a better indication 'in numbers'' what the ranges have been **. The 7 day average remains unaltered. This change for example produces: FAAH Min.-Max Hours 6.43-9.59 hours. Of course, one has to gauge for oneself what this translates to for own device(s), but it will be a better guidance I'd think for the (new) set-forget crunchers **. Maybe I'll add also a new line for the hard task limits, in CPU time of course, so CEP2+HCMD2 would be 12:00 at current standing, regardless the power of the device. Probably better placed in the Matrix... undecided. ** Exception maybe DDDT2... the B-C times are all over the place. --//-- |
||
|
|
|