If you keep a two week average of a certain client on a certain box,
it's a pretty stable number for your own use. You can also always go to
the TeamLambChop pages and get their standard WU they use for their
benchmarking. Then you can compare with everyone else using that
particular WU for benching.
-----------------
Guy Olinger
Apex, NC, USA
----- Original Message -----
From: Captain Nem <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 06, 2001 5:28 AM
Subject: Re: CLI vs GUI 3.03
>
> Was that done with the same work unit though? That's the only way to
test
> it - take the same work unit of data and run it with both clients. All
other
> tests rely on work unit specifics, which vary.
>
> Andrew
>
> ----- Original Message -----
> From: "Calvyn" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, January 06, 2001 6:33 PM
> Subject: RE: CLI vs GUI 3.03
>
>
> >
> > Jello,
> >
> > Well it seems that my CLI average has slightly increased with the
new
> > version. Here are my results..............
> >
> > v3.0 - 7 Hrs.
> > v3.03 - 11 Hrs.
> >
> > OS - Win2k
> > RAM - 384MB
> > CPU - PIII500
> >
> > -Calvyn-
> >
> > PS - I also use SetiSpy 3.0.3, available at
> > http://pages.tca.net/roelof/setispy/
>
>
>
> ==
> Unsubscribe instructions:
http://www.talkspace.net/mlists/setiathome.html
> This list sponsored by talkspace.net: building space communities
online.
> Mailing list services provided by klx.communications -- www.klx.com
>
>
==
Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html
This list sponsored by talkspace.net: building space communities online.
Mailing list services provided by klx.communications -- www.klx.com
