I've noticed that the result file size is slowly creeping up on this project. When it first started they were around 23MB and have now crept up to 31MB. Also recently, the average WU size has decreased. The result is the one machine I have running this project (a 980x at 4Ghz with 24GB RAM with BOINC installed on a RAM disk) has gone from needing 4.5 hours to 7.5 hours per day to upload it's results on a 640kbps/5Mbps up/down internet connection. It's a shared connection which I can use for about 8 hours a day so Im about at the limit for upload bandwidth. Can we expect a continuation of this trend or is 31MB the upper limit for the file size?

Wish my upload took only 6 minutes to upload. Right now it's taking around 14 minutes on DSL. I hope the size doesn't grow much more. If it does, might have to rethink coming back to this project.

The Clean Energy Project - Phase 2

Average amount of data per WU (MB) (min - max), 30.81 (24.20 - 31.89)
Average amount of data per day and per core, 89.7 MB

Memory requirements (MB)
Intel Mac OS 32 bits, 388.2
Linux 32 bits, 173.8
Windows 32 bits, 158.1

Disk space requierements (MB)
Intel Mac OS 32 bits, 2078.2
Linux 32 bits, 1086.1
Windows 32 bits, 701.9

http://wuprop.boinc-af.org/results.py

mike Hello

Did oyu read here System Requirements
it might help

Good luck

Sorry to deviate from the current topics, but I have a suggestion re. "Questions about participation drive for CEP2". I thought it may fit in this thread.
I only found out about the participation drive in the recent World Community Grid - February, 2011 Update. I subscribe to the Member News and Known Issues fora, but there is no announcement there. Correcting this might gain a few extra participants, and would also inform new members who did not receive the e-mailed Feb 11 Update, but who came across this thread while browsing the Forums, as to just which participation drive this thread refers.

[Edit]: I just started a new thread on my team's website (XtremeSystems) to help recruit more CEP2 participants - CEP2 needs more crunchers.
If no-one else has made a similar announcement on your team's website, you might consider doing something similar.
The guys at XS are computer enthusiasts who probably have a higher proportion of machines eligible to crunch CEP2 than the WCG average, so I'm hoping for a good response there.
--
[/ot]: I gave up on crunching CEP2 in its early days, when it gave many problems. Since the project seems to be struggling to attract enough crunchers, I'll give it another go.

I would like to be able to continuously run just 1 CEP2 task on each of the 3 machines, but I think the only way to do this will require micro-management, as I think there is no facility in BOINC to do this. If on the other hand, BOINC was written using the original philosophy of the institution to which the "B" refers, who also brought us BSD Unix (same "B"), we could probably run 2 independent invocations of BOINC, one under each of 2 separate users, allocating 1 core's worth of % CPU time to the BOINC process that runs only CEP2, and the remaining % to the other user's BOINC. Some problems might be solved by running 1 x BOINC under Linux, and another under WINE. However, I suspect that the BOINC server (WCG end) would reject all such arrangements due to the hardware IDs and perhaps the IP addresses being identical for the 2 instances of BOINC.

If there is a not-too-hard workaround, please let us know.
--
@Mike.Gibson: I had some troubles getting one of my machines to download CEP2 jobs too. Apart from examining the startup part of the BOINC Messages log, I found useful info in this log when my client actually tried to fetch CEP2 work and failed. To observe this, I temporarily set my machine's Device Profile (WCG end) to fetch CEP2 only, with "other work" disabled, and then on the BOINC client I gradually increased the work cache until it attempted to fetch work.
First of all - not enough memory, only 512MB. Funny, there were 4 x 512MB modules plugged in. Hmmm, the HDD had been thrashing madly since the previous night. Reboot, and BIOS says 512MB. Dead RAM stick! Now running 3 x 512MB
Then not enough disc space. Archived some large files onto DVD, and away we go ...
Don't forget to restore the Device Profile & work cache settings after you've finished testing!
[/ot]