[smokeping-users] Smokeping/FPing scalability guidelines?

Tobias Oetiker tobi at oetiker.ch
Thu Jun 19 20:55:00 CEST 2008

Hi Ged,

Today G.W. Haywood wrote:

> >
> > not sure about these numbers you have there, you say your smokeping
> > perl collector process is takeing up 1.5GB virtual memory, and that
> > it is increasing over time ? This would be some sort of leak then.
> No, not increasing over time.  Just sitting there.  A leak wouldn't be
> a big deal anyway, I could just run a restart from cron.  Yes, the
> processes are using almost 1500Mbyte of RAM.  Two-thirds of that could
> be swapped if the machine needed to swap, but it doesn't.  For the sake
> of clarity, this isn't hurting me - it was just a response to the OP.

can I have a look at your config ? my instance here is 9 MB res and 17
MB Virtual ... have you configured many forks ?

> > if you want to code, how about improving on fping and makeing it
> > scale better ?
> I didn't say I want to code, but sometimes it happens that way. :)
> I don't quite know what the best architecture would be, but my guess
> is that it would be to have a single process which does the pinging
> working with a list of hosts to ping.  This feature is present in fping
> already of course.  As I said, I imagine that the existing tools could
> do what's needed, so the first step should be to investigate what could
> be done with what's already available rather than to start coding.
> OTOH I was wondering what would happen if I changed the first line of
> /usr/bin/smokeping from
> #!/usr/bin/perl -w
> to
> #!/usr/bin/perperl
> --
> 73,
> Ged.

Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch tobi at oetiker.ch ++41 62 213 9902

More information about the smokeping-users mailing list