These sound about right for optimized client times?

[Careface]

Heya, just found a thread the other night about optimized clients, and was like O_O at the thought of faster SETI crunching.. so naturally I downloaded them.. left it running over night and found these time differences. Do they seem about right to you?

2.2GHz AXP (TBred B): (avgs)
~9600s (2h 40m) --> ~8100s (2h 15min) [18.5%]

1.5GHz Mobile Celery:
~22500s (6h 15m) --> ~13000s (3h 03min) [73.0%]

P4 3.2 Prescott: (HyperThreaded, so 2 get done in this time)
~20000s (5h 35m) --> ~11000 (3h 10m) [81%]

to be honest, the P4s time seems a little high, something is up?

Careface*

[TC]

Yeah that sounds too high for the P4. I'm getting the best results with the ipp optimized client. Which one did you use for your P4?

[Careface]

the seti-p4-prescott-sse3, do you know where I can get the ipp client? :o thanks for the reply :)

Careface*

[Dk Jedi Allianc]

I posted a thread a while ago where people could compare times on the optimized clients. You can find it here (http://www.ocforums.com/showthread.php?t=386076)

There you can see what times other are seeing.

[Careface]

ah, i found and downloaded the ipp client for p4s, and so far its done a couple of HT'd units @ ~8300s, much better than the original ~22000 it was taking with the default client.. I think seti should incorporate some kind of CPU detection thing where it checks your CPU, benches it with different available optimized clients using a standardized WU, and then download the client where it got the fastest time in.. anyway thanks for the help guys, just raised my RAC somewhat, lets say that :E..

Keep on crunching!

Careface*

[Mictlan]

As for the Celeron Mobile, the times seems a little bit him for me. I have a P M 1.5 (Banias) and was doing similar times, until I followed an article in the main page (http://www.ocforums.com/showthread.php?t=393104) about managing the Intel SpeedStep settings (and lowering the voltage of the chip to same some battery). I don't know is Celerons have the ability to achieve lower times, but you should try it. When I was testing my Laptop with SETI I found that usually I was running at 8x multiplier instead of 15x causing my times to double. Now that I have fixed the multipier (when on full usage and wall connection for power) I have shaved 50% of my time :D.

Currently doing 1.8 hours in average instead of 3.4 hours.