If classic is to be shutdown shortly there will be a bucket load of users wanting to download BOINC Manager (9.xMB), the seti client with the multi MB error annotation file and get wu's. Based on the current bandwidth load at Berkeley of 50 to 60 Mbps on a 100Mbps connection (which I assume currently includes classic), will we be struggling to connect for many weeks/months until the rush is over?

If so, then now is a good time to start multi-project resourcing.

Live long and crunch!

---

Paul
(S@H1 8888)
And proud of it!

> If classic is to be shutdown shortly there will be a bucket load of users
> wanting to download BOINC Manager (9.xMB), the seti client with the multi MB
> error annotation file and get wu's. Based on the current bandwidth load at
> Berkeley of 50 to 60 Mbps on a 100Mbps connection (which I assume currently
> includes classic), will we be struggling to connect for many weeks/months
> until the rush is over?

The BOINC client comes from an IP that's part of the Berkeley.EDU allocation, while the client and work units come from part of the Cogent address block.

... and the load on "classic" will be dropping at the same time it's picking up here.

It'll probably be tough for a few days, if that long.

... and people can always raise their caches, or pick up other projects.

---

>
> ... and people can always raise their caches, or pick up other projects.
>

Or they can come here and complain about how clueless the Seti@home team is. You know there'll be quite a few people doing that.

(btw, I was being sarcastic. I personally feel that the Seti@home team is doing an excellent job).

---

You will be assimilated...bunghole!