[smokeping-users] Re: Scalability

[Marc Powell]

One final update. Running multiple smokeping processes per collector
seems to have done the trick. As a bonus, the granularity of my graphs
has increased dramatically. I had forgotten that rrdtool will
interpolate data points for values that it didn't have up to a certain
limit. As a result, the graphs I was seeing were amazingly consistent
over 10-20 minute intervals but I didn't really see that until I made
these most recent changes. Now that the checks are truly completing
within 5 minutes, the graphs are more accurate. The fping process must
have been taking a *looong* time to complete previously.

--
Marc

-----Original Message-----
From: Tobias Oetiker [mailto:oetiker at ee.ethz.ch] 
Sent: Sunday, June 16, 2002 10:31 AM
To: Marc Powell
Cc: Smokeping
Subject: Re: [smokeping-users] Scalability

Today Marc Powell wrote:

> Tobi et al,
>
> I am really interested in scaling up my use of Smokeping
> significantly (on the order of 1500 hosts) and was wanting to get
> the lists opinion on how well this might work. My chief concern
> is how well the smokeping.cgi will behave with that many hosts to
> display. I would have a number of sub-menus and the largest
> submenu might have maybe 300 hosts in it. I know that there are
> also likely to be concerns about data collection but I plan to
> implement a number of external data collectors and rsync the rrd
> files back to the central reporting station on a regular basis.
> I've been quite successful doing this for a Cricket installation
> and don't see any major roadblocks to this. Are there any other
> issues that I might have to contend with that could be classified
> as show-stoppers? Any other thoughts?

Hi Marc,

the polling part, as long as you use fping should work fine, as for
the cgi, creating 300 graphs will take in the order of 1 minute ...
so I would suggest you order your tree in a manner that not too
many hosts are sitting on the same brance, then it should be no
problem ... Smokeping is certainly much more efficient in
generating graphs than cricket as all the graphs get generated by
the process which displays the webpage, and not through additional
processes which get launched upon dispaly of the grpah (maybe
cricket fixed this in the mean time)

tobi
>
> TIA,
>
> Marc
>
>
> --
> Unsubscribe
mailto:smokeping-users-request at list.ee.ethz.ch?subject=unsubscribe
> Help
mailto:smokeping-users-request at list.ee.ethz.ch?subject=help
> Archive     http://www.ee.ethz.ch/~slist/smokeping-users
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
>

-- 
 ______    __   _
/_  __/_  / /  (_) Oetiker, ETZ J97, ETH, 8092 Zurich, Switzerland
 / // _ \/ _ \/ / phoneto:+41(0)1-632-5286  faxto:+41(0)1-632-1517
/_/ \.__/_.__/_/ oetiker at ee.ethz.ch http://google.com/search?q=tobi

--
Unsubscribe mailto:smokeping-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi