RE: {bb} CPU Load: Windows vs UNIX

["Lose, James" <james.lose@twcable.com>]

Phil,

Thank you for the explanation. I guessed as much, but it's good to have
someone else confirm my suspicions.

I wonder why the developers of the Windows BB agent decided to use the
name "load" to describe a measurement that is incompatible with the
already established UNIX "load"? If only the code for the Windows BB
agent were freely available, like that of the UNIX agent, then I could
have figured it out and fixed the problem myself. 

Thanks, again.

Jim Lose

-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Philip
Clark
Sent: Tuesday, April 25, 2006 8:16 PM
To: bb@bb4.com
Subject: Re: {bb} CPU Load: Windows vs UNIX

On Tue, 2006-04-25 at 19:33, Lose, James wrote:
> How do the CPU load values returned by the Windows and UNIX BB agents 
> compare? Is there a way to equate the two?

The short answer is no.

As I understand it, the Windows value is utilization (the inverse of
idleness) while Unix load is based on the number of processes waiting to
run. BB multiplies the Unix "load average" value by 100 so that the
integer arithmetic can be used.

The best analogy I can think of is a bank. The Windows value would be
equivalent to the proportion of time that a teller spends serving
customers. The Unix value would be the average number of customers
waiting in the queue.

Cheers, Phil.



--
Weinberg's Principle: An expert is a person who avoids the small errors
while sweeping on to the grand fallacy.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.