Celeron&Seti

[DIRTsquirt]

I have a Shuttle SV24 1 gig celeron machine that has 128mb of ram. I just installed seti and am majorly disappointed.
Est. Time is 8hr.52mn for my first WU! That is 2.5 times longer than my 1466 xp. I was xpecting a reduced perfomance level
but man.
Is there a monitor in win98 that will tell me the cpu% being used? Does this seem out of line in terms of time per WU?
Is there any thing I could do the speed this up? ( I will not and cannot Over Clock this unit )
would an additional 128mb make any difference. or would a pIII 750 I have laying around be any faster?

 

[Baldy18]

I suspect that if you let that WU finish it will come down a little from that time but 8 hours isn't that unusual for a Celeron. Looks like you've been spoiled, my average time is 9hr 30min.

 

[OhioDude]

The Celeron suffers in Seti performance when compared to an Athlon or PIII because of it's 128KB cache size. Seti likes a large, fast cache. Eight hours or there abouts, maybe a bit less, sounds about right for a 1GHz Celery. I have two Celery 800's that are averaging right around 9 hours per wu.

 

[DIRTsquirt]

anyone out there with a pIII 750 crunching seti? What kind of times are you getting?

 

[OhioDude]

I've got a PIII 733 that averages about 8:30 per wu and a PIII 700 (100MHz FSB) that averages a little over 9 hrs per wu.

 

[Shuxclams]

I have 700@933 that are averaging 8hrs 43mins... Intel is suck.













SHUX

 

[lane42]

Ia'm using a 900 duron with 7:45 time's.

 

[Polo]

Duron 933 (FSB at 133) : 6h58 average with W2K.

 

[RaySun2Be]

Tualitin PIII800 laptop.............................5h16m <----------This ROCKS!
DUAL Xeon700mhz 1G RAM 2M CACHE....5h17m <----------This ROCKS x 2!
PIII933mhz 256M RAM, Win2K Server.....7h13m
PIII733mhz 256M RAM WIN95..................7h21m
PIII733mhz 256M RAM Win2KPro.............8h02m
PIII750mhz 256M RAM laptop..................8h14m
PIII733mhz 256M RAM Win2KPro.............8h26m
PIII1GHZ 256M RAM desktop...................8h39m
PIII1Ghz 256M RAM laptop.....................11h13m <----------IS SUCK! :Q
PIII1Ghz 256M RAM laptop.....................11h15m <----------IS SUCK! :Q
AMD 500mhz.......................................1d 1h42m <----------IS REALLY SUCK!

This is from my work herd SETIQ client stats. I expected much better from the IBM R30 1Ghz laptops, but didn't have time to research. I suspect there are some "services" running that are chewing up the cycles. Only had them for several days while setting up & burning in.

 

[Assimilator1]

Shux
There's something wrong there (or is it a Cel you've got?) ,here's the specs of an old rig I had

PIII 650 @ 820 (126 FSB),BX chipset,256Mb RAM,CAS2 ,most WU's @ 7hrs ,CLi v3.03 on Win95b

DIRTsquirt
The 128k L2 cache plus the reduced bus between L2 & CPU cripple its peformance compared to a PIII or a Tualtin Cel (1.2GHz up)

 

[JWMiddleton]

DIRTsquirt, The newer Celly2 has a 100MHz FSB. That hurts SETI performance. I have a Celly2 850 that is OC'd to 1.055 GHz (124 MHz FSB) and it has an average WU time under 7 hours. The model of your Chipset and memory settings in the BIOS also makes a big difference. For example I have four systems with Celly2 600s that are OC'ed to 900 MHz. They are all turning in times under 8 hours. This beats what other have noted here. They all have Crucial CAS2 RAM on BX or i815 based boards. Below is a sample of times from my step-daughter's system which has an older Abit BH6 mobo with the Celly2 600 @ 900Mhz.

2002 Feb 01 02:04pm... 0.489... AMANDAP... 7:32
2002 Feb 01 06:32am... 0.422... AMANDAP... 7:37
2002 Feb 01 09:40pm... 0.418... AMANDAP... 7:36
2002 Feb 02 05:02am... 0.693... AMANDAP... 7:22
2002 Feb 02 07:49pm... 0.712... AMANDAP... 7:24
2002 Feb 02 12:25pm... 0.542... AMANDAP... 7:23
2002 Feb 03 03:25am... 0.416... AMANDAP... 7:36
2002 Feb 03 05:23pm... 1.396... AMANDAP... 6:28
2002 Feb 03 10:55am... 0.739... AMANDAP... 7:30
2002 Feb 04 01:45pm... 7.379... AMANDAP... 6:24
2002 Feb 04 07:21am... 7.899... AMANDAP... 6:22
2002 Feb 04 08:07pm... 7.074... AMANDAP... 6:22
2002 Feb 04 12:58am... 0.416... AMANDAP... 7:35
2002 Feb 05 03:42am... 0.416... AMANDAP... 7:36
2002 Feb 05 06:38pm... 0.532... AMANDAP... 7:32
2002 Feb 05 11:07am... 0.538... AMANDAP... 7:24
2002 Feb 06 01:07am... 1.318... AMANDAP... 6:28
2002 Feb 06 03:05pm... 7.367... AMANDAP... 6:23
2002 Feb 06 08:41am... 0.414... AMANDAP... 7:35
2002 Feb 06 09:28pm... 6.374... AMANDAP... 6:23
2002 Feb 07 04:59am... 0.615... AMANDAP... 7:31
2002 Feb 07 08:03pm... 0.417... AMANDAP... 7:49
2002 Feb 07 12:14pm... 0.673... AMANDAP... 7:15
2002 Jan 31 03:26pm... 0.435... AMANDAP... 7:34
2002 Jan 31 10:55pm... 0.481... AMANDAP... 7:29


I have a similar system that I built to use at work and the times are close to those above even with me working on it 8 hours per day.

It looks like your SV24 has the Apollo Pro 133A chipset with integrated S3 Savage4 video which is refered to as the PL133. I suspect that box is not tuned for high performance. Download SiSandra and test you memory. knowing your memory performance will allow you to tweak it in the BIOS. Get the Sandra benchmark utility here.

Good luck!

 

[AkumaBao]