On Sun, Dec 20, 2009 at 11:02, Spike Spiegel <[email protected]> wrote: > On Mon, Dec 14, 2009 at 10:28 AM, Carlo Marcelo Arenas Belon > <[email protected]> wrote: >>> a) you are only concerned with redundancy and not looking for >>> scalability - when I say scalability, I refer to the idea of maybe 3 or >>> more gmetads running in parallel collecting data from huge numbers of agents >> >> what is the bottleneck here?, CPUs for polling or IO?, if IO using memory >> would be most likely all you really need (specially considering RAM is really >> cheap and RRDs are very small), if CPUs then there might be somethings we >> can do to help with that, but vertical scalability is what gmetad has, and >> for that usually means going to a bigger box if you hit the limit on the >> current one. > > Ime cpu isnt' really a problem, the big load is I/O and indeed moving > the rrds to a ramdisk is the most common solution with pretty decent > results.
I concur, for the moment. ;-) If gmetad takes on more duties, in terms of more sophisticated interactive access, built-in trickery for improving disk IO, etc, then CPU could become an issue. However, that's a really big "if," and a problem for the future. > I think there's a middle ground here that'd be interesting to explore, > altho that's a different thread, but for kicks this is the gist: the > common pattern for rrd storage is hour/day/month/year and I've always > found it bogus. In many cases I've needed higher resolution (down to > the second) for the last 5-20 minutes, then intervals of an hr to a > couple hrs, then a day to three days and then a week to 3 weeks etc > etc, which increases your storage requirements, but is imho not an > abuse of rrd and still retains the many advantages of rrd over having > to maintain a RDBMs. The d/w/m/y split is a good *starting point*. Ganglia needs to ship with some sort of sensible default configuration that essentially works for many/most people. You (singular or plural) are are free to customize your RRD configuration as policy and storage capacity require and permit. Ganglia officially supports this via the RRD config like in gmetad.conf. and as your storage system permits. In the ideal world, you keep all data, at the highest resolution, forever, but that usually isn't practical. -- Jesse Becker ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
