So, the latest in this grand comedy of errors is that on all 17 of my machines, I continue to get the message "No schedulers responded" ... so basically I am dead in the water.

I think a little thing called _load testing_ might have been a good idea before this project was ever let out of its cage ... but hey, I've just been working in software for almost 15 years; what do I know? :-/
Space Geeks, Inc.
http://www.flyingllama.com/sgi
Serving WU since October 20, 2002

"So, the latest in this grand comedy of errors is that on all 17 of my machines, I continue to get the message "No schedulers responded" ... so basically I am dead in the water."
Did you forget about Seti Classic? They are still up and running over there AND the rumor is that we are checking results that looked promising from the initial set of returns.

Hey, that's pretty neat! A thread noting that Seti@home isn't perfect, and offering the suggsetion that it should have been tested more.

Thanks, Rev. W! Boy, I was sure wondering when someone would be clever enough to voice this new and very unique viewpoint on the message board.

You're welcome, smartass. How unique to get a snide reply from someone on an internet message board. Gee, never seen that before.

> Hey, that's pretty neat! A thread noting that Seti@home isn't perfect, and
> offering the suggsetion that it should have been tested more.
>
> Thanks, Rev. W! Boy, I was sure wondering when someone would be clever enough
> to voice this new and very unique viewpoint on the message board.
>
>
Space Geeks, Inc.
http://www.flyingllama.com/sgi
Serving WU since October 20, 2002

Thanks for recognizing the smartass nature of my post :) I thought I was coming on a bit too strong, but I guess I hit it right on the mark.

The "beta" I think it's safe to say, was taken completely by surprise when this stuff went live.

The Dev's had JUST reworked the whole method of benchmarking, and (surprise,surprise) the website had been down for a few days!

The Beta site didn't acknowledge that it had "gone live" until 2 days after it was posted on classic.

I think it's safe to say that at least some in beta expected a "here's a release canidate and we need you to beat on it" version or two... Maybe the Alpha testers did that - all 31 of them!

Seti Boinc claims they had to go live because word got out.. Here's how Predictor (the other BOINC project) handled a load issue, just today:
---------------------------------
7/21/04
We are back online submitting new wu's! Nevertheless we are still working on our performance problems in between. For the moment we have disabled new account creation as well to not make the problems worse. We are working hard to get P@H back on track and thank you for all of your support :-)
---------------------------------

That's the way to communicate with volinteer crunchers!

Why didn't Seti/Boinc "disable new account creation" when they got flooded back in June!?

There's no excuse for the way that this system was released!