>>> On 4/11/2008 at 4:09 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > Hi Brad: > > On Fri, Apr 11, 2008 at 3:04 PM, Brad Nicholes <[EMAIL PROTECTED]> wrote: > >> I agree that the size of the XML could be reduced in most cases, however it > would be impractical to define the metrics in gmeta. The reason why is > because of the new metric pluggable modules in 3.1. Since gmond can be > extended by plugging in metric modules, there would be no way for gmeta to > know about every metric definition that could possibly exist. With the > pluggable interface there is no longer just a fixed set of metrics. Any > gmond could be gathering metrics about anything. > > How about reducing the amount of XML being sent from a gmetad to an > upstream gmetad like what I suggested in this mail? > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg03941. > html > > Cheers, > > Bernard
Yes, I think we need something like that for gmeta. What I was thinking is to add another filter type. Somthing like ?filter=delta or something like that, that would just project the delta since the last dump. If both gmond and gmetad had a way to reduce the XML by just producing deltas, I think that would speed up the XML parsing a lot and also reduce the writes on the RRDs. Brad ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
