| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Fast/reliable host |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
martin64
Senior Cruncher Germany Joined: May 11, 2009 Post Count: 445 Status: Offline Project Badges: 
|
Usually hosts are "fast/reliable" if they return results within less than 48 hours in averge, and recent results were validated, according to the FAQ (yes, Sek, sometimes I read the FAQ
---------------------------------------- but haven't found an answer to my question below). It will then get jobs with shorter deadlines, typically 4 days. Is there any way (config file or so) to prevent the host from getting these short jobs?Background: Consider a portable computer that is connected to the Internet most of the time, but then it is unable to connect for a couple of days, e.g. Monday 'til Friday. So on Sunday I would increase the buffer to get enough WUs to cover the week. Instead of cancelling all the repair jobs manually, it would be smarter just not to receive any. And BTW, the 80 tasks maximum per day and core is yet another issue in this situation if crunching HCC...  Regards, Martin  |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges: 
|
To my knowledge there is no parameter (in Preferences or in the cc_config file) to specifically forbid high priority jobs.
----------------------------------------However if the usage pattern you describe is regular (i.e. not exceptional) you should run with an extra work buffer of 6 days to avoid becoming idle. And with such a parameter together with connecting only during week ends your average return time would hardly fall below 48 hours. Regarding the daily quota (per thread) I doubt that any current notebook allows processing of more than 160 HCC jobs a week per thread (even less 240 if you connect from Friday to Sunday). But do not hesitate to tell me if this assumption is wrong.  |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges:
|
but then it is unable to connect for a couple of days, e.g. Monday 'til Friday. Re-reading your post I wonder if I should have read it differently from what you have written. If you wanted to mean that this notebook connects from Monday to Friday and not during the week end then simply set the extra work buffer to three days permanently and this device will never be considered as reliable. And obviously it will never have problems with the daily quota. ---------------------------------------- [Edit 1 times, last edit by JmBoullier at Jun 10, 2010 9:14:02 AM] |
||
|
|
martin64
Senior Cruncher Germany Joined: May 11, 2009 Post Count: 445 Status: Offline Project Badges:
|
...you should run with an extra work buffer of 6 days to avoid becoming idle. But then there are times when the computer is off, so I would have too much work buffered... I need to - well, not really micro-manage, but at least mini-manage And I don't like the idea of having so much buffer - it means that lots of wingmen (and the servers) will have to wait for my results longer than they should.Regarding the daily quota (per thread) I doubt that any current notebook allows processing of more than 160 HCC jobs a week per thread (even less 240 if you connect from Friday to Sunday). But do not hesitate to tell me if this assumption is wrong. My notebook with 2 cores does a bit more than 40 HCC results a day. So if I quickly want to buffer for 5 days, it's not really possible, can only buffer 160 max. Regards, Martin |
||
|
|
|