"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> wrote in message
news:zMvDb.6006$0s2.4594@newsread2.news.pas.earthlink.net...

"sweet" <sweet430@hotmail.com> wrote in message
news:FuvDb.201663$ri.28427773@twister.nyc.rr.com...

"Stratcat�" <none@no.org> wrote in message
news:bfpDb.12434$aw2.6552632@newssrv26.news.prodigy.com...

"sweet" <sweet430@hotmail.com> wrote in message
news:9DnDb.422680$pT1.27942@twister.nyc.rr.com...

Hi,

I have been running SETI@home for a few years now and only since I

installed

Windows XP Pro have I been able to see the amount of process time

the

application receives. It's only 50% and the other 50% is "System

Idle

Processes."

What gives??

The Windows NT OS bases the %CPU time on the total available CPU time.

This

means that in a dual CPU system (a single, HT enabled CPU is considered a
dual CPU in this case), the maximum CPU time a single thread can get is

50%.

In a 4-way system, the max is 25%.  This is counter intuitive as you would
expect to see 200% available in a dual CPU and 400% in a 4-way system.
(This is what VMS does.)

The S@H CLI client is single threaded.  If you want an easy method of
driving both processors, take a look at SETI Driver.  It caches and uses

all

the CPUs (by default).  The current version also supports true "Idle"
processing so that the off-line folders features in Outlook XP and Windows
XP get CPU time.  (yes, this is an unabashed plug for my software, but I
haven't seen any other software that allows the user to easily force the
client to the lowest priority level in Windows, which is why I added this
feature.)

Mike.
http://www.wakeassoc.com/setidriver

Both the homepage and the driver page could not be loaded at 7AM EST USA
on Tuesday, 12/16/03.

-sweet
_________________________________
sweet 430 at hot mail dot com
http://www.angelfire.com/ny5/jbc33/