> FYI they didn't want to go live as early as they did. The URL for the
> 'active' site leaked out and spread around the world through message boards.
> If this had not happened, they would have done more testing and possibly some
> load-testing of the servers. They also could have prepared with better
> hardware. Right now they are waiting on a major disk upgrade to increase
> performance in their database. The supplier they ordered it from messed up
That's not quite right Toby. They chose to take it online of their own free will. When the address was leaked they could have blocked further users from joining, they didn't. I sat and watched the discussions on the Beta boards and refrained from joining (although I was sorely tempted to) until the official announcement. When I joined my machinies got host ID's in the high 2000 numbers, so not too many had joined while it was still unofficial. They could have stemmed the tide by not allowing new users to join but instead they chose to take it live officially. I'm not even going to make a call about whether or not it was a bad decision, but just point out that it was their decision, it wasn't forced on them by the users.
> This is why they made it possible to get work from other projects as well. If
> seti@home is out of work, your client will just go on to ask predictor@home or
> einstein@home or climate prediction.net for work.
> So really, you should be happy about this since your CPU time isn't being
> 'wasted' on useless re-calculations.
And a great idea it is too, much better than endlessly crunching the same WU's for no real gain.