Subject: Re: Seti@home performance question
From: "BrianW" <brian@nospam.net>
Date: 03/05/2005, 23:18
Newsgroups: alt.sci.seti

Geoff wrote:
"Black Baptist" <pray@the.church.com> wrote in message
news:Xns963D8F6D42A46praythechurchcom@Letuspray
Gary Heston rambled on in alt.sci.seti:

In article <Xns963CF00115C3Epraythechurchcom@Letuspray>,
Black Baptist  <pray@the.church.com> wrote:
I have to computers pc1=duron 1.3 ghz with 1 gig of
ram pc2=intel 2.6 ghz with 512 megs of ram it took
pc1 22 hrs to complete a unit and pc2 18 hrs to
complete a unit. Shouldn't pc2 do a unit twice as
fast as pc1?

Depends upon more than just clock speed. Is the 2.6 a
Celeron, while the
1.3 is a true P4 (or even a P3, which outperformed the
equal-clock-rate P4 chips)? How much L2 cache is in
each system? What motherboards are in the systems?
Cheap motherboads can run 30-40% slower than a good one
with identical CPUs in the. Memory type/speed and FSB
also affect performance.


Gary


PC1: AMD Duron 1.3 ghz L2 64, 1 gig pc2100 ddr sdram
specktec ram motherboard Biostar M7VIG Pro FSB 133 PC2:
Intel Motherboard FSB 233 Cpu Intel 2.6 GHZ 512 pc2100
megs of pc2100 ddr sdram specktec ram.

i get the idea you are running seti@home classic gui version

you should uninstall it and install the boinc version of seti:
http://setiweb.ssl.berkeley.edu/sah_participate.php
doing this will certainly speed you up, the old classic gui was badly
slowed by the graphics

you prob have a intel celeron (celery) 2.6ghz cpu, you fell victim to
the mhz myth (google it)
don't worry about it too much though
22 hours and 18 hours is very slow though, more info needed if the
above didn't help

That's about how long my antique 333 mhz P2 takes to process a work unit. My 
decent (around 2 ghz) machines take around 4 hours (or less). Have a look in 
task manager when you're doing nothing, to make sure it has 100% CPU or 
thereabouts. Something is seriously amiss. If you're using BOINC, don't 
select the screensaver, or it will revert to screensaver mode every time you 
leave the PC unattended. Select "blank screen" as your screensaver. Not that 
this will account for more than a fraction of the problem. (Even if you told 
it to use the screensaver when you installed it - like I did on one PC - you 
can easily overcome this from desktop properties.)

Brian