posted July 13, 1999 13:21         

My average unit time went down from 37 hours on the K6-III to about 15 (!) by using the Linux client that doesn't calculate these silly spatial analysis animations.

Put the text client in the same directory with the graphic equivalent and run it with the -stop_after_process option so it will terminate without trying to make a connection while you're offline. If you run your machine while you're absent you can nicely combine that with the RC5-64 client, which will use the computer once SETI is done with the unit

IP: Logged

posted July 14, 1999 14:45         

IP: Logged

posted July 14, 1999 15:36         

It would seem that the FPU characteristics between pipelined FPU (Celeron) and low latency (K6) do not weigh in so heavily in FFT calculations.

Now if we get a real-life speed factor 2 for 3DNow! we could get maybe 4 units out a day on the K6/450 core

IP: Logged

posted July 18, 1999 06:30         

And now you tell me (that the NT version works on 98 too), after you made me try all the tricks to get it even a bit faster, heck I even used the Linux version!

Well, thanks for the tip, if these 'optimizations' keep pouring in at this pace, I don't need any 3DNow! version at all! In fact, soon I'll be able to run my K6-2 266 on 266 MHz instead of 350

The graphical windows client V1.00 takes some 62 hours to run, V1.05 takes 28 hours, Linux takes 18 hours and now, this!

IP: Logged

posted July 18, 1999 12:07         

IP: Logged

posted July 18, 1999 22:28         

Hope that helps some

IP: Logged

posted July 19, 1999 01:57         

IP: Logged

posted July 21, 1999 11:08         

I have a k6-2 266 with 128MB RAM clocked at 4x75 running win95 24/7.

SETI is running all the time in the system tray, and the screen-saver bit of it is disabled (replaced by blank screen).

So far, my average time per unit is 28.8 hours. Can this be improved upon? (without instaklling a different OS!)

Thanks

Ian

------------------
Ian Riches
Bedford, UK

IP: Logged

posted July 21, 1999 15:47         

IP: Logged

posted July 21, 1999 17:46         

this is my first post here.

The 3DNow project for SETI is fascinating, can't wait to see the times.

The quickest way to run SETI is through Linux or NT.

My K6-2-350 @ 400 (4x100) can do a WU in Linux in around 15hours. I have a cheap mobo. With a better mobo I think this could be much better. It's better to up the bus and down the multiplier if possible.

Check out

http://discussions.hardwarecentral.com/Forum5/HTML/001096.html

We are way into over there.

Not trying to poach anyone here, but we welcome anyone to our team.

http://setiathome.ssl.berkeley.edu/cgi-bin/cgi?cmd=team_lookup&name=team+anandtech

Anyway, good luck getting into the top 100.

later,

Col.

------------------
Witty comment in signature field.

IP: Logged

posted July 21, 1999 17:56         

I see anyone leave our team for Anandtech's team.. and well... I might have to get upset..

Seriously the 3DNow Team(s) are designed to show the potential power of the 3dnow user base, and we are only starting to build these teams.

Regards,

Steve

------------------
It will go faster!

IP: Logged

posted July 25, 1999 09:28         

1.) Use a utility such as Norton Tools or Nuts and Bolts to take a permanent swap file and make it the first file on the Hard Drive. This makes the file much more efficient and also places the window components together so the drive isn't constantly seeking between the two sides of the permanent swap file for it's components.

2.) When not needed close all other programs. Use a util from MS Kernel Toys called WinTop to monitor the cpu usage. The problem here is even 0.05% of cpu usage will load things into both the L1, L2 and if you have it L3 cache This will cause some other things to get kicked out and or reloaded into cache! This could cause a major slowdown with the unoptimzed version as remember they are talking memory latency pulling data into cache to keep the cpu fed.

3.) disable the clock on the task bar and set it to auto hide. This should eliminate cpu usage of the explorer.exe in wintop.

4.) Of course use the Comand Line Interface or I386nt. Just place it into the same directory as the gui you installed. Make a shortcut in the startup folder and tell it to run minimzed. This way you don't forget to start it.

Hope this helps others!

[This message has been edited by tanware (edited July 25, 1999).]

IP: Logged

posted July 25, 1999 12:58         

IP: Logged

posted July 26, 1999 18:21         

hope to have helped,

Colin

IP: Logged

posted July 27, 1999 01:26         

Oh well, it prol only would've been good for about 1 a week.

IP: Logged

posted July 29, 1999 06:51         

I found that disabling "Auto Insert Notification" for CD-ROMs and CD-Rs can decrease WU proccessing time by 1 to 10%. Slow computers gain the most (300MHz and below).

Best Regards

MrHeat

IP: Logged