On Mon, Oct 10, 2011 at 7:54 PM, Japheth Cleaver <cleaver at terabithia.org>wrote:

On 10/10/2011 12:10 PM, T.J. Yang wrote:

...

Hi, All

This is a question we got asked a lot when trying to deploy a xymon/hobbit client onto a production system.

How much system resource(cpu/memory) will xymon/hobbit client consumes ?

Any one has a script or C program on doing this measurement ?

Procedure:

1. Deploy xymon client
2. Run this program for 3 days.
3. Here is the report of xymon cpu/memory usage for past 3 days.

I am interested to tackle this task but hopefully some one already did this work and willing to share.

Regards

tj

I ran this at $currentjob-- and the load was literally indistinguishable. We even ran rotating :30s sadc collectors, fired off in 1m increments (to get high-detail last-5-minute metrics in the client reports for analysis in status-change logs) and noticed no change whatsoever in non-broken boxes.

If things like 'df' and 'top' cause appreciable load, the box is probably already in bad shape.

If you want to reduce generic impact even further, think about things like having /dev/shm/ as your BBTMP (on linux), or firing xymonclient.sh off via SSH call or cron as an existing user (no xymonlaunch = 1 less daemon).

I use cron for most clients. I just had to put a couple of environment variables in at the top, for BBHOME & BBTMP (I think). I also cut out the various compiled binaries and went with curl to post the status message to a php script on Xymon secure web server.

Ralph Mitchell