From: Thomas Guyot-S. <de...@ae...> - 2009-01-27 09:11:10
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/01/09 03:52 AM, Yann Jouanin wrote: > I agree about the modular backend would be the best solution. > > I also agree about the fact mysql server could decrease performance, this was the reason I thought using sqlite could be a best idea. > Things is that the way Nagios reads status (reading everything even when you apply a filter) drive it really slow (as an example I have more than 7000 services on a server and need more than 10seconds to get the page). Are you sure it's not spending time in CPU cycles? If you have enough RAM the whole status file should stay in memory and be fast to access regardless of your disk speed. On my setups I put my status.dat, checkresults and temporary files on tmpfs mount points to avoid IO on the FS log anyway (even if the data changes too quickly to end-up on the drive, file systems with logging will always write to their log whenever you make a change on the fs). > I may help you to create the modular backend if you want (and if this have a chance to be commited of course!) The database stuff itself could be modular and allow multiple SQL backends btw, so an SQLLite database would best fit there. I'm not sure how CDB would perform in the normal CGIs without heavy modifications as they read all data anyway, but the php interface should fetch only the required data; therefore a CDB file would be very fast. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJfs+m6dZ+Kt5BchYRAjxRAKCiVqa7gObBBR/gdUSqi2iiswb/DwCfYkFl mDoDbHuBNMa+U/CvNR3MnSk= =tqlI -----END PGP SIGNATURE----- |