Stratcat wrote (Re: SETI@home receives only 50% CPU time?) :

If you're running a single instance of CLI 3.08 &
convert to CLI 3.03(s), you will see an additional ~ 10 -15% increase in
production vs. the CLI 3.08's

Does this mean CLI 3.03 is more efficiently coded than 3.08 ?
Is that hyperthreading specific, or does it go for all x86s ?
I thought I had noticed my averages going up when I upgraded, but I also
upgraded to XP from 98SE at about the same time and thought it was due to
all those XP services chewing up cycles.
Somewhere on the BOINC list someone said that processing SETI WUs under
BOINC would take ~30% longer.

As an old programmer in assembly code (remember that?  ) as well as in
higher level languages, I well understand the value of using high level
languages to be platform-independent, keep down the cost of development and
on-going maintenance, but when the main objective is to crunch as many WUs
as possible, surely newer versions should always be leaner and meaner than
the old.

In the Folding@home forum they are discussing joining BOINC and the best
size for WUs from a users psychological point of view - IMHO if you earn a
'gold
star' every hour, that has to be more fun than one every thirty-three hours.

sweet wrote :

only since I installed Windows XP Pro have I been able to see the amount
of process time the application receives

For Win 98SE users the same info can be got using WinTop
(download from http://www.dewassoc.com/support/useful/wintop.htm )
Norton System Works also includes Process Viewer which does a similar job,
but you can't change anything.