I was just wondering how many users/hosts that the CPDN boinc servers are expected to be able to cope with when it goes live ?

If the predictor and seti servers are still having teething problems at that point , is there any danger of CPDN boinc being overwhelmed and if so will the account creation facility be temporarily capped to try and avoid the problems the other projects have had when dealing with large loads untill it is known just what the servers can handle ?

Shady

My guess is that the larger workunits will equal less server traffic and therefore more users before a crisis develops. Hopefully by that time the problems at seti will have generated a solution so CPDN will never have that crisis.

But this is only a guess, your actual milage may vary.
<br>John Keck
BOINCing since 2002/12/08

From what I've read, most of the problems the other projects have had (other than hardware / network problems) is problems dealing with the number of work units distributed, validated, etc. CPDN should work better since there's less work units to validate in a day.

Hopefully, new problems won't be created using boinc 4.x server / client.
---
<IMG SRC="http://www.funkymonkey.org/boinc/sig.php?id=925&amp;proj=pah"> <IMG SRC="http://www.funkymonkey.org/boinc/sig.php?id=169421&amp;proj=sah"> <IMG SRC="http://www.funkymonkey.org/boinc/sig.php?id=360&amp;proj=cpdn">

The work unit splitters are the weaker parts but i think it'll be better in this project since it has laaaarrrrrgggg workunits

But if seti problems keep on coming the cpdn project will get lots of attention and may have some problems too!

&gt; The work unit splitters are the weaker parts but i think it'll be better in
&gt; this project since it has laaaarrrrrgggg workunits
&gt;
&gt; But if seti problems keep on coming the cpdn project will get lots of
&gt; attention and may have some problems too!

My main worry is that to download the CPDN/BOINC application requires 8MB of downloads (the monitor program, common data, climate model executable etc) -- so if 10K sign up in a short time that's 80GB of bandwidth needed.

I think workunit "delivery" which has been tough to keep stable on other BOINC projects is not that bad for us, only 10KB of files needed from one workunit to the next, and they happen in 3-6 weeks on average.

So my plan is to get two more scheduling servers in addition to this server (climateapps2) online by next week so help divvy up the big 8MB downloads (that first big initial download when you attach to CPDN with your BOINC client; not to forget the 1-2MB for downloading BOINC as well).