<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 23 May 2013 08:31:52 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Mike Willbanks' Blog: PHP Performance Series: Maximizing Your MySQL Database]]></title>
      <guid>http://www.phpdeveloper.org/news/10443</guid>
      <link>http://www.phpdeveloper.org/news/10443</link>
      <description><![CDATA[<p>
<i>Mike Willbanks</i> has posted <a href="http://blog.digitalstruct.com/2008/06/18/php-performance-series-maximizing-your-mysql-database/">another part</a> in his "PHP performance" series today. In his <a href="http://www.phpdeveloper.org/news/9711">previous article</a>, he talked about caching techniques including things like opcode caching and database memory tables. This time he talks about getting the most out of your MySQL database.
</p>
<blockquote>
Application level SQL performance is much different than the performance of the SQL query itself but rather how it has been designed to work in the application. Many of the items I will be addressing in this area is designing your application to make less queries thus improving scalability and likely performance. However, performance does not always equal scalability as the same with scalability does not always equal performance.
</blockquote>
<p>
He looks at a few different topics like lazy connections, iterating queries, need-based selects, normalization and a few simple things that you can apply to every SQL your application uses to optimize it as much as possible.
</p>]]></description>
      <pubDate>Thu, 19 Jun 2008 12:01:24 -0500</pubDate>
    </item>
  </channel>
</rss>
