Re: [SLE] SETI work_Units on SuSE Linux 6.2
I have a PIII 500Mhz 992.87 BogoMips 1 work unit takes just over 9 hours Maybe you haven't turned on the K6 optimizations in the kernel. Are you running it as a 386? Best regards //Anders PS. I also have a WinNT with the same CPU and mem size. One work unit there takes over 20 hours. Odd, isn't it On Fri, 12 May 2000, tabanna[SMTP:TABANNA@AIG.FORTHNET.GR] wrote:
Hi, SuSErs :)
On a Pentium 133 mhz, 1 SETI work unit took 30.2 hours. On an AMD K6/2 1 SETI work unit takes 15 hours ______________
Linux rated the Pentium 133 mhz as 53 bogo mips Linux rates the AMD K6/2 500 mhz as 999 bogo mips ______________
Why does the AMD K6/2 500 mhz seem to be lazing around with the SETI work_units . . . SuSE 6.2 ain't 'Slackware' ? !
?
Maybe its a Floating Point matter, with Fast Fourrier Transform ?
Any views, please ?
best :) -- ____________ sent on Linux ____________
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Maybe you haven't turned on the K6 optimizations in the kernel. Are you running it as a 386? ...........................
~ Hello, Anders :) ~ you know what - I have now rebuilt kernel, but, there is no improvement in the speed of processing SETI data-units ! . . . my AMD K6/2 500 mhz only does SETI twice as fast as my old Pentium 133 mhz, although the Pentium 133 was rated at 53 bogomips, and the AMD 500 mhz at 999 bogomips. ~ Curious ? best :) Richard Harrisson Aegina, Greece. -- ____________ sent on Linux ____________ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Maybe you haven't turned on the K6 optimizations in the kernel. Are you
running
it as a 386? ...........................
~ Hello, Anders :)
~ you know what - I have now rebuilt kernel, but, there is no improvement in the speed of processing SETI data-units ! . . . my AMD K6/2 500 mhz only does SETI twice as fast as my old Pentium 133 mhz, although the Pentium 133 was rated at 53 bogomips, and the AMD 500 mhz at 999 bogomips.
It take about 20-24 hours to get a seti unit done on the AMD 300 mhz here, I forget the bogomips and not at the machine right now. if you get one of the newer seti clients, they run nice by default, might want to check that, turn it up a bit. Also how much ram do you have compared to the 133 machine? the second version of seti are slower than the first version, did you upgrade your seti client in the process of upgrading your proc? Check the seti faq for more info on this. omething I just thought of, and I will try it when I get home, is to `renice` the seti process during non-peak hours (ie when I got to bed or am at work) to -9 (forgot the nice properties under linux, check `man nice; man renice`) using a crontab. This way, the seti process is allowed to eat more resources, off the topic of my head (this may have errors in it) ps aux | grep setiathome | renice --1 `awk '{print $2}'` Also are you running the seti command line version, or seti the GUI version, don't run the GUI, it is bloated and takes more time to finish units. Jack -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
anders.johansson＠modul1.se -
jbarnett＠axil.netmate.com -
tabanna＠aig.forthnet.gr