seb wrote: >> I was able to write to database and I already have setting to removed >> the oldest data from database. So problem was somewhere else. > > It seems to me ndo problems are often related to mysql performance... > On my smallish nagios test instance (50 hosts - 300 services), the > db weighs ~300 Mb / 1M records, and everything works fine since > I switched to innodb storage engine. Don't know whether it's really > related (table locking vs. record locking)... > I think ndo is able to cause a good deal of stress to any "untuned" > mysql server, the README could be updated to include a couple > of tuning tips (innodb pool sizing, small query cache as most > requests seem to contain variable arguments, pre-allocating > innodb storage, etc..). If a mysql wizard reads this, please give > your advice :) >
Just adding some few indexes to the database would help the load enormously. I remember Ton Voon giving a speech at Nagios Konferenz in germany last year, stating that analyzing the queries and then creating the appropriate indexes boosted performance by as close to 300000% (querytimes dropped from 146secs down to 0.2). This is off the top of my head though, so take the numbers with a grain of salt. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
