<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mysql on iniy.org</title><link>https://iniy.org/tags/mysql/</link><description>Recent content in Mysql on iniy.org</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 12 Apr 2024 10:59:39 +0000</lastBuildDate><atom:link href="https://iniy.org/tags/mysql/index.xml" rel="self" type="application/rss+xml"/><item><title>Find slow-queries in MySQL</title><link>https://iniy.org/2009/10/find-slow-queries-in-mysql/</link><pubDate>Wed, 14 Oct 2009 21:26:31 +0000</pubDate><guid>https://iniy.org/2009/10/find-slow-queries-in-mysql/</guid><description>&lt;p&gt;Often when a web-application seems slow it&amp;rsquo;s not (or not only) the parse time, but also or mayorly database speed. Most scripting-languages don&amp;rsquo;t act &amp;ldquo;intelligent&amp;rdquo; in parsing as it would be best for user experience, but go through the code line by line (whom would expect it otherwise?). So if you have a website containing some slow MySQL-Queries it seems as if all the page just takes a eternity to load. One step would be to put all the page loading into some seperate code-piece and load it later with ajax-technology. This gives a great boost in user-experienced speed, because the most parts of the website load and are already usable before the database content pops in. But otherwise often not the database is the problem, but bad written querys. But how to find them? Luckily mysql already provides us with a feature called slow-query-log which can be activated easily through my.cnf. So just look for this:&lt;/p&gt;</description></item></channel></rss>