Trouble with latency

[Herb J.]

You may wish to periodically off-load the historical data to a second 
database and clean up the primary one periodically. Having a smaller 
database would help immensely when NDO periodically truncates old data.

Also, make sure that you have the proper database table indexes created. 
Also consider converting the tables to InnoDB. The default install of 
NDO doesn't have things fully optimized as well as it should be for 
large installations. Missing indexes would also cause MySQL to hang 
while searching the tables for old data to remove, and with MyISAM the 
table would be locked during the delete.


On 07/06/2010 09:37 AM, Scott Ward wrote:
> The problem with that is that we need to retain the information for at 
> least 6 months possibly more.
>
> ~Scott Ward
>
>
> On Tue, Jul 6, 2010 at 8:35 AM, Assaf Flatto <nagios at flatto.net 
> <mailto:nagios at flatto.net>> wrote:
>
>
>     Scott
>
>     I encountered a similar issue with ndo and mysql when the tables
>     grew to
>     a monstrous size , and ndo had trouble doing the updates to the DB.
>
>     Check the tables sizes and see if you can trim them to a more
>     "manageable" size.
>
>     Personally i truncate the tables that  grow to fast every week as the
>     data i need the ndo for is never more then a day old .
>
>     Assaf
>
>     Scott Ward wrote:
>     > I am having major latency problems, 700 seconds in some cases.  I am
>     > pretty sure that it is coming from ndo and mysql.  Anybody have any
>     > mysql configs or changes to ndo that can help.  Right now I am using
>     > the default ndo config and made some changes to allocate more memory
>     > to mysql and that's pretty much it.
>
>
>     --
>     Never,Ever Cut A Deal With a Dragon
>
>
>
>
>     ------------------------------------------------------------------------------
>     This SF.net email is sponsored by Sprint
>     What will you do first with EVO, the first 4G phone?
>     Visit sprint.com/first <http://sprint.com/first> --
>     http://p.sf.net/sfu/sprint-com-first
>     _______________________________________________
>     Nagios-users mailing list
>     Nagios-users at lists.sourceforge.net
>     <mailto:Nagios-users at lists.sourceforge.net>
>     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
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>
>
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100706/248915de/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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