Compariing performances.

[Alessandro Ren]

    I've recently installed the broker in my nagios running in Fedora 
Core 3 after having solved that null pointer bug and I'd like to share 
some performance information with the list to see if my server is 
running as expected and exchange some code change idea to boost performance.
    Attached there are five graphs with informations from the system and 
nagios it self.
    My HW is a P4 2.8Mhz, Sata 80GB and 1GB of memory. This Nagios has 
2500 services beeing monitored, besides nagios is running with perfparse 
and storing the data directly in the mysql database, we have also Nisca 
collecting network statistics and it has already 20 milion records in 
its database.
    I'm worrying a little about the HW requirements for bigger setups 
with the broker and what could we do to boost performance.
    I've changed the perfparse code a little so it does not save all the 
performance data in on table, but it divides per host, each host has its 
own table where all the performance data for all services are stored 
there, so the tables are much smaller than one big table, I wonder if 
this could not be done with the broker, for long term storage, some 
tables can get very large.
    Just sharing some though with the list to exchange some ideas.

    Thanks,  []s.
   

-- 
__________________________________________________
*Alessandro Ren*
	/*OpServices*/
/*Luciana de Abreu, 471 - Sala 403*/
/*Porto Alegre, RS - CEP 90570-060*/

*(*   phone 55(51)3061-3588
*4*    fax 55(51)3061-3588
	*Q*   mobile 55(51)8151-8212
*:*   email alessandro.ren at opservices.com.br 
<mailto:%22alessandro.ren at opservices.com.br%22>

__________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20060324/18b7230d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: resources.png
Type: image/png
Size: 20519 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20060324/18b7230d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: entropy.png
Type: image/png
Size: 6139 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20060324/18b7230d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: latency.png
Type: image/png
Size: 11542 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20060324/18b7230d/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: load.png
Type: image/png
Size: 19429 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20060324/18b7230d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: problems.png
Type: image/png
Size: 6749 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20060324/18b7230d/attachment-0004.png>