19+ hours on an athlon 750? same as a k6-2 350 in linux?

[Redem]

I have a athlon 500@750 and it takes 19+ hours to complete a seti w.u. Now, i didnt think much of this until i set up my linux server to.. and it takes 19+ hours too, well closer to 20 but anyways.. What is wrong with my athlon setup.. ?. Im running the client as a screensaver and the setup of the computer is.
Classic Athlon500@750 1/2 cache div.
Asus k7m mobo
128Mb pc133 ram
leadtek winfast geforce 256
3c905tx network
tekram 390F scsi
dvd/cd/cd-rw on scsi
ibm 34 gxp 13Gb hd
and so on..

now.. is my setup slow or is the linux computer fast..
(linux k6-2 333@350, 64Mb pc100, 3c905tx, 3c900, set as router for 10Mbit internet connection. running samba..)

Is seti very integer dependent or something?

 

[Poof]

<< Im running the client as a screensaver >>



That's why. The Linux client is a text client (unless you ran xsetiathome) and you're comparing to something graphical (which takes CPU cycles).

If you want to run the screensaver, make sure you go into the display properties for the screensaver and set it to go to blank. That should bring the times closer to its optimum.

If you want the best times, run the windoze text client.

 

[Sukhoi]

Poof is correct. Make sure you run it in blank screen mode.

Redem, are you on the Team AnandTech SETI@Home team? If not, join us!

 

[Redem]

Ofcourse I am.. im currently on like 400:th place but im climbing .. Thanks for the advice.. it runs more then twice as fast when i set it to blank..

 

[BadThad]

Try running the text version for winNT. Your times will drop even more. Be sure to set the screen to go blank still.

 

[networkman]

Even the GUI version should complete a unit in 8.5 hours.. at least that's what my Athlon 750(non oc'd) does a unit in(that includes all the times I use it for other stuff too.)

 

[JWMiddleton]

networkman: I am amazed that an Athlon 750 takes that long? :Q I have a PIII-550 OC'ed to 733 and it has an average of 4 hrs 40 mins. I dropped it by .5 hours by changing the memroy to CAS2. I assume your Athlon is the orignal with off-die L2 Cache. I would also assume that the Thunderbird would be MUCH faster? Did Cli v.3.0 improve your time?

Just wondering as I had thought of building an AMD box as my next project. Does anyone have time on T-bird with DDR ram?

 

[Redem]

Nice.. I downloaded seti driver and seti spy.. also I installed cli.3.0 version.. no If i'm supposed to belive the estimate.. it say 2h 28min.. :/. on both seti drver and seti spy.. this seems like too much of an improvement.. . And when i compared the preformance of the cpu, it came out on top.. over the alpha.. 2.34CpF.. hmm.. is this info correct?..

 

[JWMiddleton]

Hi Redem, Need to let it run a while longer! The total time calculations start low and then change a bit. You really need to let it run for a few days and look at the SetSpy log to see the results. It seems that the more you watch it, the longer it takes!

 

[Poof]

<< I dropped it by .5 hours by changing the memroy to CAS2. >>



Wow JMiddleton. In the system in my sig, I'm OC'd to 800 and getting around 5.5 hrs as an average (with WUs that have an angle range in the 0.4xx range). High angle range WUs give me about 4:40.

I know that there's an almost 0.5 hr add-on running it in linux as compared to windoze. But I'm also running my PC100 RAM at CAS3 now (it is CAS3 RAM but since it is decent Mushkin, it could run at CAS2 all the way through an OC to 700... after that it wouldn't POST @800 until I changed it back to CAS3 ).

Since the RAM prices continue to drop, guess it's time for me to get some PC133 or even some of that Kingston PC150. Maybe I could try running the CLI on my Linux via WINE too...

 

[blade47]

I just thought I'd chime in. My P3-500e@620mhz using cas3 ram is averaging 5:54hrs using v3.0 cli in WindowsME.

I'm thinking along the same lines as Poof. Since prices are so low I'm considering ordering some PC-150 or PC-133 ram. I'm kinda leaning towards the Mushkin PC-150.

 

[Sukhoi]

JWMiddleton, I'm pretty sure they're talking about original Athlons. Remember that the original Athlons had the slow cache, so that's probably why the WU times are slower than PIII's and T-Birds.

 

[JWMiddleton]

I went to a computer show yesterday and picked up 2 x 64MB PC133 Infineon SDRAM that I am running at CAS2. I got them for $70 plus tax. The last four WU's are as follows:

4.474
4.359
4.056
4.504

This is on a Soyo 7VCA (Via 694) MoBo with a PIII-700/910 (130 MHz FSB) I have the BIOS set to TURBO, CAS2 and 4-Way interleave.

So yes, this IS the time to buy memory. Unless, you rather upgrade to a system with DDR ram.

 

[networkman]

Hmm.. now I'm thinking that I need some help!

My Athlon 700(OC'd to 900) takes about 5.5 hours per WU, but this is also my gaming rig so that may account for the slower times. I have my ram at CAS2, but this is a 100fsb... any other suggestions?

 

[Assimilator1]

Are you able to enable super bypass? (I asssume its the 100 MHz only memory board?)