Posts by Kevin

1) Message boards : BOINC client : Feature Request: Hierarchical project ordering (Message 36814)
Posted 10 Feb 2011 by Kevin
Post:
Well, 4 day buffer isn't enough -- I've run out of work to do. So either:

1. It's been down for over 4 days now
2. The buffer estimator needs a little work. :)
2) Message boards : BOINC client : Feature Request: Hierarchical project ordering (Message 36713)
Posted 3 Feb 2011 by Kevin
Post:
You could increase your cache setting to a couple of days, then you are unlikely to run out of work,



This might be useful to do as then I could span server downtime and "no work to do", assuming that period doesn't stretch more than a couple of days.

It would be in keeping with my desire to get Seti work done as primary, but I wonder if I might actually be slowing down the Seti effort.

Think about it -- I'm hogging extra work units, so to speak, that "everybody else but me" would probably get done faster. On the other hand, the downtime puts a much bigger monkey wrench into this -- a million computers start spinning their wheels, making a mockery of efficiency, so to speak.

Now if everybody had a 3 day cache to buffer over the down time, even more work would get done.



Yes, this is a pipeline type operation, where the important thing is average throughput. Therefore a large cache, keeping my computer working 100%, would be beneficial.

Ok, I will try the larger cache.



ETA: Ok, set it to 4 days. Advanced --> Preferences... --> network usage --> Additional work buffer == 4.0 now (if that's the wrong place, tell me)
3) Message boards : BOINC client : Feature Request: Hierarchical project ordering (Message 36645)
Posted 28 Jan 2011 by Kevin
Post:
I run Seti exclusively. However, sometimes it has no work units to do. I would like my BOINC to do work units for something else in the downtime.

I tried adding a second project, but that just lets me split active CPU effort between the projects -- I want 100% on Seti when there's Seti to do, and 100% on something else, and only when there's no Seti work to do, if you follow that.


Seti seems to put a pause in every week or two while they're messing around with their servers, freeing up 1-3 days of doing nothing.

I note this would only be useful in practice if the "timeout" for processing a work unit for my "backup" project were longer than the Seti up/downtime cycling. (And, to a lesser extent, if I could get at least one work packet done per downtime.)





Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.