• 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.

Question for Seti "Seniors"

B

BarneyFife

Diamond Member
I'm fairly new to seti. I've only been doing this about a month. I wondering what the wu times were back then. Back when this project started, the top of the line cpu was a p2 450 or so. Were wu's easier to complete? I'd imagine a wu taking 17 hours on a 450 right now. Did they take 17 hours to complete back then?
 
I can't remember..... :Q

Seriously, I wasn't running SETI before the 3.03 version, but I heard that it was faster....

Good question though! 😀





plus I needed a 1st post, as well as post trying to keep ahead of Engineer's neffing.... 😉😉

 
I remember finishing WU's when I started with the GUI on a celeron 466@584 in I think about 8 hours. With the release of version 3.03 the client did "more science" but everone suspected that just made it take longer as seti wasrunning out of WU's to give out and bandwidth was becoming a problem.
 


<< The 3.03 GUI client took about 80-90 hours per WU on my K6-2 380 :Q
TNOguy >>



Argh, and theres me thinking that I should get my K6-2 350 back up running again so it can crunch SETI... 😱

I'm not a SETi senior, sorry Barney.
 
A kindly bump up. 🙂

Man, this place is starting to feel like OT, where threads disappear off the front page quickly. It used to be a thread would hang on the front page for a day or so, and give everyone a chance to see it. Now I find myself bumping up threads daily just to make sure they are seen, read, and responded too. :Q

😉😉

😀

A good sign that a lot is happening with Team Anandtech, and a good sign there are a lot of active members! 😀
 
The old GUI app was quicker than the 3x series. Much quicker, but they made you upgrade to continue contributing.
 
I started with a BP6 i(400 C's OC to only 500) n October 1999, the client was 1.03 (1.01b for the GUI if I recall) average wu 18 hours. Then there were new clients every 3-4 months in the 2.0 series by December 2000 a P2 @ 600 was doing them in about 5 hours. Then Feb 2001, 3.03 client introduced and the 5 hour wu times became 8.

Now the p4's and xp's are 3-4 hours.

Curiously, I reserected that old BP6 and its doing about 16 hours a wu... on the 2.03 client
🙂
 
Yep, the older clients were considerably faster than the newer 3.x versions, supposedly because these new versions are doing more science. Not all of us actually believe that, but that's the "company line" as it were. One of the real brains around here could probably say for sure, but I ain't one of 'em.. at least not today anyway. :Q 🙁


 
I was pretty happy running the Cli on an overclocked P3 700E @ 978Mhz before version 3 came out. I was getting 3 hour WU's and now with version 3.03 they same system takes over 6 hours. It is examining the data much more thoroughly.
 
Well, I'm probably in the running for the "most" senior around here so...........................what was that question? 😱













Ha LOL j/k I remember who Barney Fife was. 😀 😛
 
I am kinda new to the program....but i've been going at it for about a month or two i'd say....and i started crunching on....
Pentium1 MMX 233@266mhz using the 3.03 CLI....using just setispy.....and i was able to do about 1 wu every 20 hours...
and thats where most of my comp time came from...but heh....i will soon be moving up now...ever since i got the Athlon..
seeya
 
The stats here are what i did with the GUI (not sure which version) on my K6-233, same comp now with the CLI takes about 60hrs per WU 🙁

My athlon takes about 5hrs 15mins with the 3.03 CLI 🙂

ConfusedBW
 
The 1.3 client used to take 6 hours on my SparcII 400s.

I think it took 15/16 hours on my K6-2-350 (at 4x100).

It was optimised to use bigger amounts of cache so it was really quick on Xeons and Sparcs but slower on PC type processors.

🙂

Col
 
Back in Oct. '99 when I started, it was taking my K6-2/333 ~27hrs/WU with the 1.x linux client. This was all before they came out with the windoze CLI (windoze was GUI only). Back then, I believe the fastest processors were the alphas - thus helping to justify Compaq's position (as owner of the alpha tech from DEC) in the Team standings then.

Speed-wise, the 2.x CLI on Xeons kicked butt. I was getting 4 - 5hr WUs on my original Xeon II 400 1MBs. The 3.x CLI took that up to ~11hrs/WU.

But, in all of our discussions and arguments about the move by Berkeley to double the 2.x WU times with the 3.03 client, basically to save bandwidth while supposedly getting more analysis done, we find that once again, AS PREDICTED, leaps in technology have gotten us back to where we were just before the 3.03 client came out. 😉 The ole 3-4 hr/WUs.

So now what? Many of us, including folks here at TA, offered Berkeley other solutions to help stave this off and all were ignored. So I guess we'll eventually have some new client that'll double the times again (with very little scientific gain, IMHO)... :frown:
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top