Re: Cricket Performance

Thanks for the info. My server has 4 CPUs and plenty of memory. I was able
to get the scan times under 5 minutes by splitting the subtrees into
different collector calls. 

 

  _____  

From: Angelo Deflorio [mailto:[email protected]] 
Sent: Thursday, June 08, 2006 12:57 PM
To: Levin, Craig A.; [email protected]
Subject: R: [cricket-users] Cricket Performance

 

I've been monitoring about 600 routers some years ago, having non so much
CPU power on my cricket servers. 

Having so much target to collect you have to use multple collectors, with
high CPU usage and cricket web interface slow down.

 

My solution was to split the two basic cricket functions (collector and
grapher) and to spread the collector function across a pool of servers.

In this case I used:

- one front end Linux server (RH70), apache equipped, hosting the cricket
configuration and cricket data exported via nfs, used to browse collected
data.

- three back end Linux servers (RH70), linking the same front end nfs for
config.db and rrd database, each one collecting its portion of data (about
200 devices) all the time.

 

Hope this helps.

bye

 

angelo

 

 

  _____  

Da: [email protected]
[mailto:[email protected]] Per conto di Levin,
Craig A.
Inviato: giovedì 8 giugno 2006 20.10
A: [email protected]
Oggetto: [cricket-users] Cricket Performance

I am having trouble monitoring over 3000 devices. 

1.	Is there some optimizations that I can implement? 
2.	Is there an archive site to research this and other questions? 

 

Thanks.

_______________________________________________
cricket-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cricket-users