Steven,
Am 08.03.2014 um 00:29 schrieb Steven North <swn(a)ocsystems.com>:
Thanks for the suggestions. It turns out we were only looking at
about 10,000 metrics per minute going through a single agent. The agent was running at
about an average CPU load of 50% (which seems high), with periodic spikes to 100-150% for
1 second (while collection was happening). I did a local setup which logged about 20,000
metrics per minute and saw a much lower average CPU load for the agent (<5%) and with
periodic 1 second spikes to 90% CPU during collection. I had to run with 512MB heap, but
only seemed to be using half that.
what version of RHQ are you looking at?
In 4.10 (hopefully out very soon), we have addressed a good number of issues - especially
one where the agent core itself was using a lot of cpu to select which metrics to take.
Also the heap usage should be considerably lower, which should also reduce (CPU for)
garbage collection and memory pressure.
The other aspect to take into account is the plugin's getValues() method, which also
has sometimes potential for improvement.
But let us know when you have findings that we can incorporate (pull-requests welcome :-)
Heiko