| Subject: Re: Boinc Priority, Part 2 |
| From: Roger Halstead |
| Date: 13/09/2004, 06:55 |
On Sun, 12 Sep 2004 20:12:27 +0100 (BST), raj@rijhwani.org (Raj
Rijhwani) wrote:
On Sunday, in article
<9EN0d.1138$eL3.41@newsfe1-gui.ntli.net>
ml_news@ddnospamddml1dd.co.uk.dd "Martin 53N 1W" wrote:
How long is your commitment?
MY committment (to any project I am attached to) is for the life of the
project, or as long as circumstances allow. I can't say that for any
particular machine, though. And I'm not prepared to commit resource
to a project which doesn't have a reasonable degree of flexibility,
resilience and allowance for component failure. It's moot anyway, because
I am never going to sign up to BOINC anyway. It just struck me that a 12
month work unit was a poor decision in project design in principle.
You're missing the point on how the Climate WUs are processed.
Periodically the system returns information and you are given credit
so the 4 week, or one year WUs are really treated as if they are a
whole succession of smaller WUs. For instance mine has accessed the
home site 6 times in the last 4 days. It has a total of 120 hours CPU
time and has done about 15% of this WU.
OTOH BOINC also processes seti WUs and they run close to the times
produced when running the command line app, so I don't follow your
reasoning about BOINC.
Two of my machines are running seti and one is running the climate
prediction app on BOINC. The 4th is running the command line version
of seti.
Roger Halstead (K8RI & ARRL life member)
(N833R, S# CD-2 Worlds oldest Debonair)
www.rogerhalstead.com