3.0 -> 3.03 client slowdown

[Ees]

A picture is worth a thousand words.
(Bonus question: how many words are two pictures worth?)

Observe the difference between clients 3.0 and 3.03 (setiathome-3.0*.i686-pc-linux-gnu-gnulibc2.1),
on two (of four in the same machine) Xeon-550's (1M cache).

3.0:



3.03:



- The 3.03 client takes more than 1.5 times as long to complete a WU.
- The speedup of 3.03 at the end of most WU's seems to be even more pronounced.
- The slowdown halfway through each WU seems to be a little less pronounced.

I'm not sure about the speedup and slowdown effects (could be my imagination, or just an artifact of those particular WU's). The slowdown is real enough though. Not that it's unexpected, but it's a sad sight nonetheless.

Martin

[Ees]

Restoring the natural flow of time...
(Last one.)

Martin

[Swing]

I wonder what the difference between clients 3.0 and 3.03 is when using an Intel Coppermine or AMD T-Bird [smaller cache].

[cjolley]

It's a LOT!
chuck
(Former member of Seti@MURC top 5 fastest list )

[Wilt]

The increased time in 3.03 is due to a change in the chirp rate to a +-20Hz/sec. This needs a lot of more FLOPS to finish a WU.

As the SETI pages says, this is to make more science... and to limit the bandwith used for the connections to their servers. More processing time, less connections...

[Muad'Dib]

"I wonder what the difference between clients 3.0 and 3.03 is when using an Intel Coppermine or AMD T-Bird [smaller cache]."

I'm running an 800 T-Bird @ 950 (8x119 stock vccore) and times went from @ 8 hours (which is really long I think) to 12 hours!!!

That answer your question? This really sucks! Anyone want to help me speed these up somehow?

Thanks
Dimitri

[Liquid Snake]

Yep. Just upgraded my P3-750@825 (7.5x110) to 3.03. Unit times are around 7:30 now (was 4:40 before). I didn't expect such a massive slowdown. It seems that the times are similar to what I had with 2.4 (also around 7 hours). Oh well, everyone else will have to upgrade, so the increased times won't matter too much.

[cjolley]

Actualy, in a way the times will matter because the science will be better!
This is a good thing.
Though right now (while I "compete" with people running 2.7) it doesn't feel that way
chuck

[Muad'Dib]

Ok, help a dummy out would ya guys?

Explain to my why (even though your times have gone up Liquid Snake), they're still faster than mine even though you're running 125Mhz slower than me?

I'm confused....

Thanks guys.
Dimitri

[Liquid Snake]

Have you tried the Optimization Guide at Pace's site? http://www.setiatmurc.f2s.com

My friend's 1GHz TBird does units in about the same time as my machine in 3.0 (not upgraded to 3.03 yet). No overclocking of any kind done. The RAM runs at 2-2-2 and 133MHz (FSB is 100). Also, if your system is constantly under heavy load, SETI will slow down, since SETI is designed for using idle CPU cycles.

[DentyCracker]

Haven't switched my Duron to 3.03 yet but I've switched the 550 at work and the time to process a wu has gone from 7.5 to 12 hrs. Haven't been to the other machines recently, will try to change them soon. Have a linux box running as well but it always ran 3.03 so can't compare. Setispy 3.03 reports 4.x teraflops to process with 3.03 as opposed to under 3 with 3.0. I hope they level the playing field soon.

[Grego]

Using the 3.03 GUI a wu took about 10 hours, compared to the 5 hours/wu when using the cli v3.0.

My system is not oc'ed

------------------
System:
Asus A7V rev. 1.01p bios 1004.c
AMD Thunderbird 800
SBLive retail with liveware 3.0
Matrox g400 MAX
LG Flatron 795FT 17" monitor
IBM 13.5 GB 7200 hdd
Pioneer 103-s dvdrom
Win98 1.st edition
directx 7.0a
128mb pc133

[agallag]

Wow, my P3-600 can do WUs in around 9-9.5 hours using 3.03. I guess it's faster than yours because, being a Katmai, it's got 512KB of cache...

------------------
Andrew
Carpe Cerevisi

[Muad'Dib]

I can't for the life of me get Pace's page to load. I can't figure this out.... Oh well.

Dimitri

[Dyre]

Well, im still on the same WU since the update... The WU was almost done before (~8hours) i upgraded.... So its re-doing it.

Im at 57%, 21hours!

Lame