As Sowulo says somewhere in this thread, You don't give that many details
when you're dealing with a lot of computers and customers each day.

It is true, that when using HT and one CLI, Windows reports 50% CPU usage,
and I KNOW that it'll be probably a bit more, as it is Windows that is
unable to report the correct usage.

However, that is not the information that Philips wanted. He wanted to know
why his WU takes such a long time, and I think he now knows why.

Futhermore, out of experience, I can assure you, that running 2 instances of
the CLI on a HT system puts out more WU's a day. I don't care that much
about WU-time, but I care about WU-output.

When I have a rack of 16 HT enabled machines they turn out about 1.5 times
more WU's, then when I turn HT off.

So my advise to everyone with a HT enabled machine is:
1: if you have the money, go fot a AMD 64 bit CPU (sorry, I'm on the
AMD-camp ;-) )
2: run 2 instances of the CLU to increase overall output
3: when WU-time is important, turn HT off in the BIOS, reinstall Windows and
run only one WU.

Willy.


"Stagger Lee" <SLee@houston-hunks.com> wrote in message
news:878125677.7545464722@houston-hunks.com...

On Thu, 06 Nov 2003 18:17:28 GMT, Sowulo <bosco@UFO.com> wrote:
: *snip*
:
: > Running two work units simultaneously will not lead
: >to the improvement you have predicted.
:
: I don't see any prediction other than running two at once will slow
: down your times but increase your overall production and this is most

In the original post, Twisted Hardware wrote:

"You probably have hyperthreading enabled, so SETI can only use 50% of

your

CPU. You should use the CLI in combination with a tool to run 2 instances

of ..."

: certainly accurate information.  That 3.0c should be turning out about

Then perhaps you'd better take a remedial reading course.  The claim by

Twisted

Hardware is utter rot.

In other words, the phrase "can only use 50% of your CPU" is baloney.