Is anyone experiencing a high load with gmetad? I've run this daemon on
a high end intel 933mhz dual proc machine with 1gb of memory and RH
7.2. Loads get and stay as high as 3. I get worse results on single
processor machines, loads as high as 6.7 Kill the daemon and it drops
back to normal.
markp wrote:
Is anyone experiencing a high load with gmetad? I've run this daemon on
a high end intel 933mhz dual proc machine with 1gb of memory and RH
7.2. Loads get and stay as high as 3. I get worse results on single
processor machines, loads as high as 6.7 Kill the daemon and it drops
b
I'm using it to monitor a 260 host linux cluster. The old perl web-frontend
didn't exhibit this type of behaviour. I'm seriously thinking of going back
to it.
Steven Wagner wrote:
> markp wrote:
> > Is anyone experiencing a high load with gmetad? I've run this daemon on
> > a high end intel 93
mark-
i've seen this behavior on the machine running the ganglia demo page but
it's just a p2 with 128 mbs of memory (soon to be upgraded).
i'm rewriting gmetad in C right now and will be incorporating it into the
monitoring-core distribution soon. the biggest bottleneck right now with
gmetad
Remember that RRD files are of a fixed size. In other words, they should
never grow beyond their original size when created. That's why they call
'em round-robin databases. :)
So the only reason new RRDs would be created is if new metrics were added
for existing hosts or if new hosts were ad
5 matches
Mail list logo
