FW: [TEST/REVIEW] CPU accounting patches

[Mullen, Adam]

Yes, I clearly understand.  My point still stands though, if an admin
wishes to use power saving techniques for whatever reason, that choice
shouldn't deter the rest of us from gaining a more precise
accountability for our CPU cycles.  Thus why I suggested a blurb be
added with this patch stating the ramifications of using power saving
techniques with this method of cycle sampling.   

-----Original Message-----
From: Garance A Drosihn [mailto:drosih at rpi.edu]
Sent: Friday, January 27, 2006 1:02 PM
To: Mullen, Adam
Cc: arch at freebsd.org; freebsd-current at freebsd.org
Subject: RE: [TEST/REVIEW] CPU accounting patches

At 12:39 PM -0600 1/27/06, Mullen, Adam wrote:
>Lets see here though, how many of us have a 100 node beowulf cluster 
>who use FreeBSD daily?  I know I don't!

That isn't the question I am answering.

The question was "Who in their right mind users power saving features on
a server OS?".  And the answer is "People who run LOTS of servers".

That is all.  I'm not saying *you* have to run power-saving features.  I
am saying that there are people who use a SERVER operating system, and
who have very good ($$$$$$$$$$$$$$$$) reasons to care about power
consumption.  People who on the one hand do want infinite CPU power, but
still have to balance that desire with the monthly bill for energy and
cooling.

-- 
Garance Alistair Drosehn            =   gad at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu




This message contains confidential information and is intended only for the individual named.  If you are not the named addressee
you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as
information could be intercepted, corrupted, lost, destroyed, received late or incomplete, or could contain viruses. The sender therefore 
does not accept liability for any error or omission in the contents of this message, which arises as a result of e-mail transmission. 
If verification is required, please request a hard-copy version from the sender.