>So I'd like to ask the Ganglia community -- do you guys find Ganglia >to be a resource hog?
No. But once I had a couple hundred gmetad processes on a 2GB server. When the size of active processes and RRD files in tmpfs exceeds physical memory, the server begins swapping and can't keep up with the needed polling intervals. Buy more memory or use more gmetad servers to solve this. :-) And I don't really like that the XML is huge and mostly redundant and gets even larger in 3.1. All gmetad needs is name and value to do correct metric rollups. All units and other attributes appear to be ignored, except by the frontend. It would be cool if, for example, we could define what a "load_one" is in one place, instead of thousands of machines reporting the same exact text every few seconds which seems like a waste of time and bandwidth. I understand the benefits of XML, but perhaps the standard static attributes could be defined in gmetad instead of gmond. This could reduce the XML size considerably and make it more efficient. But this would require a big change; just an idea to think about... -twitham ------------------------------------------------------------------------- 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
