We here at Prima Worldwide are running a quad CPU server in 24/7 workload (run always) for CP.net and it is still saying it is going to take 1000 hours to process the 4 work units we have. I know that on a small home unit that it will take 3-4 weeks to do a work unit, but our server should have better preformance than 1 month to process 4 results right?

BTW Our server is a quad (Intel 3.06Ghz Xeon) processor system with 3 GB of ram on win2003-server so there is no lack of power or memory. Our preformance monitor says we are 100% CPU usage as well.

Any suggestions or comments?

This time is only slightly long. CPDN WUs are HUGE. Figure about the saqme number of weeks that S@H takes hours. 600MB temp space / WU.

jm7

Sounds reasonable to me, assuming that is 2 real and 2 virtual CPUs. If it is 4 real CPUs there may be a problem. What kind of workload does the machine have excluding BOINC/CPDN? CPDN can be fairly heavy on the file system too, so even with low CPU usage a file server may have trouble producing the expected amount of progess due to I/O bottlenecks.
<br>John Keck
BOINCing since 2002/12/08

well on a single Xeon 3GHz one month seems a bit long, it should be more than 3 weeks, but for a quad-proc that's a "throughput" of a model finished every 9-10 days so that's very fast! And with BOINC the "cobblestones" should work out to similar amount of work on other projects.

We are running 4 real CPUs. As for workload, we only have momentary super heavy workload that may last 10-30 seconds / hour. Other than that 10-30 seconds the machine is idle(1-2% workload). The file system/storage is housed on a 5 hard disk(5x120gb mirror storage all SCSI) raid system with 120GB total storage, so access times and swap file times should be very low.

&gt; Sounds reasonable to me, assuming that is 2 real and 2 virtual CPUs. If it is
&gt; 4 real CPUs there may be a problem. What kind of workload does the machine
&gt; have excluding BOINC/CPDN? CPDN can be fairly heavy on the file system too, so
&gt; even with low CPU usage a file server may have trouble producing the expected
&gt; amount of progess due to I/O bottlenecks.
&gt; <br>John Keck
&gt; BOINCing since 2002/12/08
&gt;
&gt;