On Jan 25, 2008 9:06 PM, Bernard Li <[EMAIL PROTECTED]> wrote: > Hi Jesse: > > On 1/25/08, Jesse Becker <[EMAIL PROTECTED]> wrote: > > > Interesting. > > > > How about introducing a new metric: cpu_speed_current. For systems > > without cpuscaling, it is forced to the same value of cpu_speed, or > > not sent at all, since it is completely redundant. Otherwise, it > > reports the current CPU speed, as determined by /proc or /sys. > > I believe the CPU speed is collected once at startup -- what if the > CPU speed was clocked down (or up) after gmond started and this > "current" speed was collected -- then it no longer is current.
That's my point. The current behavior is collect the speed once, and if it potentially variable, report the maximum speed. That's fine behavior. > The other option is to collect this metric periodically, but probably > only do this if scaling is enabled. Yep, that works too. It certainly doens't need to be collected/sent frequently. I'd think that once a minute is probably ample. > But do people really need this feature? :) Actually, I can think of a good use for it: proving reduced power consumption. If you can point to a chart that shows you are actively throttling CPUs, that's a bonus for the people with clipboards and checkbooks. :-) This is all pretty minor stuff though. -- Jesse Becker GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0 2720 0083 0931 9A2B 06A2 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
