[TriLUG] MySQL Runaway

[John Vaughters]

After all the tuning and purging is done, if you are still having issues. Consider these ideas.
 
* If data is mainly read only - consider indexing tables but be cautious if there is alot of writing to the database, it may make it worse.
* You may need to question if the App is playing nice with the database. Are the queries in the App being responsible?  Many times an App is created, but the long term performance was not in the Developers mind and they just got it to work with poor query consideration. Does the App limit queries with pages for example, instead of give you everything in one shot.
* Has anyone created automation that is slamming your database and creating an unintentional denial of service?
* Last resort - Get a bigger box
 
Good Luck,
 
John Vaughters


________________________________
From: Ron Kelley <rkelleyrtp at gmail.com>
To: Triangle Linux Users Group General Discussion <trilug at trilug.org> 
Sent: Wednesday, May 8, 2013 9:49 AM
Subject: Re: [TriLUG] MySQL Runaway


You might also want to look at the "mysqltuner.pl" script.  It analyzes your currently running MySQL instance and will provide a very good analysis (completely with tuning recommendations).  We used this heavily while getting our WordPress installs working in our environment.

Just google for "mysql tuner".


Thanks,


-Ron