SETI times on Linux?

[movinslow]

Hi

I decided to run SETI on Linux(Mandrake 9.1 for now) instead of XP. I've noticed that my times are 4.5 hours. In Windows, they were 3.5 hours.

What happened? I'm running i686-pc-linux command line from the SETI site along with lin-seti.

Specs:
ECS K7S5A
XP 1700 @ 1.52GHz (138x11)
512MB PC 2100 Crucial
ATI Radeon 8500

Need anything else?

 

[Intelligence3]

I've seen several things that say that the linux code is not optimized well. I still run it on linux on my laptop just to be different, though.

 

[MoFunk]

What are the system specs?

 

[movinslow]

^ specs bump

 

[RaySun2Be]

yeah, Linux processes the WUs a bit slower. What will really bend your mind is that at one time, running the WIN CLI using WINE in Linux had the fastest processing time. 🙂

 

[Polo]

SETI linux client is slower on normal and great angle range WU but is faster when crunching VLAR WUs.
On my XP1800+ with 256 Mb SDRAM :
Normal WU takes 4:10 with W2K and 4H40 with linux
Great angle range WU takes 3:45 with W2k and 4:05 with linux
VLAR WU takes 4:40 with W2K and 4:10 with linux

As Ray said, the best times are achieved when running the windows text client under wine on a linux box (a few minutes faster on my machine).
A good solution if you have a fleet is to run a queue server like SETIQueue and a least one linux box. SETIQueue will give her the VLAR and your windows machines will be happy.

 

[movinslow]

Polo, 1800+ with SDRAM??? That's crazy! 😉 Do yourself a favor and get some DDR. 😀

Thanks for all your help. I might try WINE.

 

[Chumpman]

Originally posted by: RaySun2Be
yeah, Linux processes the WUs a bit slower. What will really bend your mind is that at one time, running the WIN CLI using WINE in Linux had the fastest processing time. 🙂

That'll really bend your noodle.

 

[Polo]

Movinslow, my mobo is an ASUS A7V133 with the KT133a chipset. It doesn't support DDR... 🙁

I think I'll soon upgrade to a P4 2.6c with a I875 chipset. I want to test hyper-threading. 😉 🙂