On Fri, Feb 04, 2011 at 02:35:35PM +0100, Ulrich Windl wrote: > Lars, > > you are right, and I saw that my guess to use /proc/stat was wrong. top is > slow in getting the current CPU usage. So basically I wondered if you need > the CPU usage at all. If you'd switch to "load", you could get it a lot > faster. > > To be honest: I wondered what "HealthCPU" would monitor about the > CPU's "health" when initially looking into it. I was kind of > disappointed to see that it simply inspects the CPU usage (A CPU that > is 100% busy (0% idle) may be quite healthy) ;-)
"Health" was arguably a bad choice, "Utilization" may have been more appropriate. But try to define "cpu health"... A box with 0% idle may not be able to take much more cpu load, so if we can use that information for resource placement, even migrate some (known to be cpu intensive) resource off of that node, obviously with some sort of dampening hysteresis (that's what the attr_updater -d 30s is for), then that is useful. I was just commenting on non-equivalent code transformation, not on the usefulness of that agent in general. I personally think that using "green yellow red" for cpu utilization is not very useful. But apparently misch found some use case, otherwise he'd not submitted that agent. It all depends on how you use it. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
