Subject: Re: benchmarking
From: "~misfit~" <misfit61nz@yahoomung.co.nz>
Date: 06/05/2004, 02:39
Newsgroups: alt.sci.seti

Stratcat� wrote:
"~misfit~" <misfit61nz@yahoomung.co.nz> wrote in message
news:pA6mc.770$XI4.35864@news.xtra.co.nz...
Nick M V Salmon wrote:
"~misfit~" <misfit61nz@yahoomung.co.nz> wrote

How much slower? I've returned a few units from a couple of my
machines since the change and they don't seem any faster. Maybe
I'll have to wait for a larger representitive sample to see the
difference?

V3.08 worked out at about 15% slower overall than v3.03 for me but
that was a while back, so maybe they re-compiled it..? Hmmmn, the
v3.08 .exe is dated March 28th 2003 on the alien ftp server, so I
don't think it's been re-compiled. I wouldn't worry about it, you'll
see it's much faster in the longer term for sure - that's why most
'dedicated crunchers' are still using it. ;-)

Thanks Nick, your advice and experience are always welcome.
--
~misfit~

Is CLI_3.08 completely removed from your Seti @ home folderer? You
may want to verify SetiDriver is 'actually using' the new client.

Yep, manually deleted it and replaced it with 3.03.

Open the Setispy GUI & Select 'Client' from the L.H side icons. - The
first line should read: "Seti @ home client: Version 3.03 (text
version)".

Everyone I know that's done the switch, after I suggested it,
including myself, usually sees a solid 10% increase. This is on
fairly recent iron (w/i 2 - 3 years old, or so).

Hopefully, with a few more units under the belt, that will be the same for
me.

BTW - The benchmark page referenced by Benjamin hasn't been updated
for nearly a year, due to various reasons. The benchmark WU he
referenced is the correct WU for the old benchmark page, though. I
ran it off in just over ~2:10:00, but don't get your hopes up too
high, 'cuz like I said, the page is almost a year old. ;-)

To get some long term #'s & averages, you may consider adding
SetiWatch to your config. Double click on the SetiDriver sys tray
icon to open up SetiDriver's GUI & tick 'Create SETLog.csv. Then d/l
& run SetWatch, but not SetiLog:

http://members.shaw.ca/mloukko/SETI.html

All this can be done on-the-fly, w/o shutting down. As soon as the
current WU finishes, SetDriver will create the .csv file, & you'll
now have loads of totals & averages info, as time goes on. You can
even export your data to an Excel (or other) spreadsheet, but I
haven't tried this feature, myself.

If you want to switch from CLI_3.08 to CLI_3.03, w/o the hassle of
ending the current WU, or waiting for the end of the current WU's
crunching, there's a method I stumbled on, that I posted near the
bottom of the 7th post down, in this old thread:

http://tinyurl.com/2hn92

Works for me, but Mike O's, prolly the best guy to comment on this
method, though.

Thanks Strat.
--
~misfit~