As a recent convert from S@H I have been looking at transferring some resources to the CPDN project. In my limited experimentation so far on both Win32 and Linux systems, the memory footprint for the CPDN client appears to be around 45-50 MB compared to the 16MB or so of the Seti client.

Is this by design for the project as a whole or have I been unfortunate to download a particularly heavy chunk of the code. If by design, then this would rather preclude, or at least be a negative factor in running CPDN on live systems such as web/file servers which are idle and underused a lot of the time, and in many ways the most ethical platform to run DC projects on as they are powered up 24/7 by necessity. 50MB could be an appreciable proportion of the memory on a small webserver, which will benefit from all available resources at peak usage.

I shall probably stick with S@H on such platforms and run CPDN on workstations, it at least sits quietly on a chair in the corner eating up unused CPU cycles rather than occupying half the sofa :-)

> As a recent convert from S@H I have been looking at transferring some
> resources to the CPDN project. In my limited experimentation so far on both
> Win32 and Linux systems, the memory footprint for the CPDN client appears to
> be around 45-50 MB compared to the 16MB or so of the Seti client.
>
> Is this by design for the project as a whole or have I been unfortunate to
> download a particularly heavy chunk of the code. If by design, then this would
> rather preclude, or at least be a negative factor in running CPDN on live
> systems such as web/file servers which are idle and underused a lot of the
> time, and in many ways the most ethical platform to run DC projects on as they
> are powered up 24/7 by necessity. 50MB could be an appreciable proportion of
> the memory on a small webserver, which will benefit from all available
> resources at peak usage.
>
> I shall probably stick with S@H on such platforms and run CPDN on
> workstations, it at least sits quietly on a chair in the corner eating up
> unused CPU cycles rather than occupying half the sofa :-)
>

That's about right, runs around 50 meg on my machines
<a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=3"><img src="http://www.teampicard.net/templates/fisubice/images/phpbb2_logo.jpg"></a>

Maybe they took this out of the email they send out when you join, but my email (invitation to join beta) explicitly said that CPDN would take up 50 MB of RAM as well as up to 500 MB of hard drive space. And of course there is the whole 1 month to process a work unit... I hope they didn't take it out because I think people should be warned. CPDN is not for the faint of heart :) 50 MB isn't much for me to spare (have 1 GB) but I can see it being a problem for older systems.
<br>
----------------------------
A member of The Knights Who Say Ni!
Yet another stats page: <a href="http://boinc-kwsn.no-ip.info">http://boinc-kwsn.no-ip.info</a>

&gt; Maybe they took this out of the email they send out when you join, but my
&gt; email (invitation to join beta) explicitly said that CPDN would take up 50 MB
&gt; of RAM as well as up to 500 MB of hard drive space. And of course there is
&gt; the whole 1 month to process a work unit... I hope they didn't take it out
&gt; because I think people should be warned. CPDN is not for the faint of heart
&gt; :) 50 MB isn't much for me to spare (have 1 GB) but I can see it being a
&gt; problem for older systems.
&gt;

I remember some time ago seeing this now that you mention it. Probably on the board before the project opened up. It definitly eliminates my oldest machine a 200mhz thinkpad with 64Mb and a 3Gb drive. Thanks for the reminder. I've been blanketly adding this project on the other boxes as I went to 4.05 and probably would've done the same on the antique.

Skip

And at least under Linux, assuming the code naming is accurate, seems to be optimised for i686 instructions, ruling out Pentium Classic based machines.

There must be a fair few systems of that generation sidelined to firewall or family file server duties, which would make ideal contributors.

&gt; Maybe they took this out of the email they send out when you join, but my
&gt; email (invitation to join beta) explicitly said that CPDN would take up 50 MB
&gt; of RAM as well as up to 500 MB of hard drive space. And of course there is
&gt; the whole 1 month to process a work unit... I hope they didn't take it out
&gt; because I think people should be warned. CPDN is not for the faint of heart
&gt; :) 50 MB isn't much for me to spare (have 1 GB) but I can see it being a
&gt; problem for older systems.
&gt; <br>
&gt; ----------------------------
&gt; A member of The Knights Who Say Ni!
&gt; Yet another stats page: <a> href="http://boinc-kwsn.no-ip.info"&gt;http://boinc-kwsn.no-ip.info</a>
&gt;

And people NEED to check out what thay are getting into, like reading the following <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/tech_faq_boinc.php">Read and Ye Shall Learn....</a> Even with the info in the email, I have seen post by people that are using boxes that are way low on the requirements scale.


M7 <b>CPDN, Berkeley's Staff Friends Club ©</b>

&gt;Thanks for the reminder. I've been blanketly adding this project on the other
&gt;boxes as I went to 4.05 and probably would've done the same on the antique.

Normally this is not a problem as the BOINC system will not allow computers that can not complete the work to download it. However I think Carl still has some of the checks turned off for testing purposes and is not concerned about missing the deadlines.
<br>John Keck -- BOINCing since 2002/12/08 -- <a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=191"><img border="0" height="80" src="http://191.cpdn.sig.boinc.dk?188"></a>

I'm not sure how I missed this whole thread, but in our BOINC workunit definitions we have a "lower limit" of 64MB, so machines coming in with less than that will simply not get a workunit (similar to how we only send out workunits to hosts that have 600MB free). This seems to be err on the side of "conservative" so I think people are OK in that it won't go to their machine if they are low on memory or disk space.