O.K. - BOINC has some serious problems.

I'm not going to defend them. I'm not going to kick 'em.
Everyone has thier personal feelings on this, and much bandwidth
has already been used, and I've got nothing worth adding to the pro-con
argument.

But I'd like to give an object opinion :

BOINC SAH2 has serious probs, as is obvious. They have been at the
edge from the getgo, with nearly continous probs. They also have some
major architectural probs. When running on the edge, there is no room for
error. When error occurs, it not only shuts down the project, but has an
'after effect', since the project has been running marginally to begin with.
Therefore, any problem causes a domino effect lasting much longer than
the duration of the problem per se, since there will be a period of lag time
as the marginal infrastructure has to recover to meet pent up demand.

With this in mind, I'm going to suggest that SAH2 BOINC will be running
intermittantly, at best, for the near term. I'd define near term as ~ 2
weeks minimum, and I'd leave the maximum open-ended.

So I guess I'm stating the obvious: Based on whether one agrees with the
above, one can choose to continue to run SAH2, and deal with it, or use
thier cycles for another project, or not at all. Simple objective fact. To
each, thier own.

As for me personally, I'm on the fence with this one. I like the science
behind SAH, and like getting in on the ground floor of a proj. At the same
time, I run another project I also started from day one, and am currently
#232 worldwide, slowly climbing, and attempting to break into the 'top 200'
page. It's a project I really enjoy and have been running my reources on it,
shared 50/50 w/SAH. A temporary SAH hiatus would double the other proj's
O.P, giving me a nice bump towards my goal. Since SAH2 is down or out of
work 1/2 the time, I doubt I'd lose a great deal of ground with it.

Yeah, I won't attempt to be overly altruistic, I CAN be a statswhore.
More critically, I build my machines specifically w/DC in mind, and hate
to see 'em go idle, or even worse, crunch data worthlessly. It's not just
science, but my enjoyment of DC as a hobby. And as a hobby, above all,
it nust be FUN! Optimizing, configuring, and troubleshooting, are fun, to a
point. Getting a new project running and debugged, and being part of the
debug process is fun, to a point.

Gonna' have to 'sleep' on this one.

JMNSHO's, as usual. ;-)

Strat