• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Scaling of Seti@Home classic client

G

Genx87

Lifer
I now have Set@home running on 5 machines in my house. For shats and giggles I noted how long each one of them takes to finish a dataset.

Here are relevant facts about the machines.

1. A64@2200Mhz + 1GB PC-3200
2. AXP@2200Mhz + 1GB PC-2100
3. P4 Mobile(512KL2) + 512MB PC2100
4. Athlon TB@800Mhz + 1GB PC133
5. K6-3 @400Mhz + 512MB PC133

Machines in order of time to finish datasets

1. A64=6 hours
2. AXP=19 hours
3. P4=38 Hours
4. A800 = 64 hours
5. K6-3 = 151 hours

To me the difference between the A64 and AXP fascinates me. Both are the same clock but one is 3 times faster than the other. I am suspecting this is due to the low latency memory controller of the A64. The K6-3 I expected to be dog slow with its lack of a pipelined floating point unit. But the P4 also surprised me as it seemed to be a bit slow for having a 1Ghz lead on the Athlon 800.

I am curious is anybody else has any kind of results and would like to post them to this thread.
 
Sounds to me like you are running the screensaver instead of the client version with setidriver as your times are way slow for those machines.
 
What are you getting for WU's per day, 3 or 4? You should be doing way better than that.
I run:

XP 2200+
XP 2800+
XP 3000+
P4 2.6
P4 HT

I am getting anywhere from 35 - 50 WU's per day, depending on AR for the WU. My average WU completion time is a little over 3 hours. Most of my machines are running on 512mb of memory also.

If you are using the GUI, dump it and get the CLI version. Mucho faster......
 
Originally posted by: Freewolf
Sounds to me like you are running the screensaver instead of the client version with setidriver as your times are way slow for those machines.
Click to expand...

indeed, my 2500+ @ 2.1 does them in about 3.5 hrs or less.
 
Ahh I didnt know the screen saver was slower than the actual client. Yes I have been running them in sc mode.

Ok Ill not run them in SS mode and see how it works out.

 
Hehe I learned something 😉

After forcing it to run all the time on my Athlon 800. The time to finish went from 36 hours to about 8 from what I can tell. I am just estimating it due to how much was done when I checked and how long it was working on the current data set. (40% done @ 3 hours CPU time)

Thanks for pointing out my obvious problem. I am surprised the SS mode degrades performance sooooo much.

Ill test out the other machine over the next few days and see how it scales with the better setup.

 
Most of the extra time for the SS is a result of CPU power being suped for drawing the graphics ,if you had of run it minimised it would of been a lot faster😉 ,however even then the text client is still about 25% faster.Going from SS maximised to the CLI(text) will lop off about 75% off WU times!😀

In the days before v3.03 the GUI used to be only about 5% slower than the text client when minimised,gods know what they did to v3.03 to change that! :roll:

8hrs sounds about right for an Athlon 800🙂

It'll be interesting to see if the Ath64 is still x3 faster than the XP
Btw the faster memory your Ath64 has will help it too.

I have an Ath XP2400 @2.22GHz ,177MHz FSB (dual channel) which does most WUs in about 2.3hrs 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top