<?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, 15 May 2008 22:50:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stuart Herbert's Blog: More about Performance Tuning]]></title>
      <guid>http://www.phpdeveloper.org/news/9566</guid>
      <link>http://www.phpdeveloper.org/news/9566</link>
      <description><![CDATA[<p>
Based off of a <a href="http://www.phpdeveloper.org/news/9538">previous article</a> from <i>Mike Willbanks</i>, <i>Stuart Herbert</i> has posted some of his <a href="http://blog.stuartherbert.com/php/2008/01/31/more-about-performance-tuning/">own thoughts</a> on tuning and tweaking your applications for the best performance you can get out of them.
</p>
<blockquote>
There's some good advice in there, and I thought it'd be a good idea to quickly add a bit more detail about the separate approaches that Mike raises.
</blockquote>
<p>
He <a href="http://blog.stuartherbert.com/php/2008/01/31/more-about-performance-tuning/">goes over</a> the APC caching, memcache, the "gzip trick", the "Not Modified" header and optimized SQL statements.
</p>
<p>
He also mentions one thing that <i>Mike</i> didn't mention - a split between static files (no PHP needed) and their dynamic cousins. Having a more pure Apache (no PHP installed) can help give a minute jump in speed that, depending on the size of the site, could really add up from a user's perspective.
</p>]]></description>
      <pubDate>Tue, 05 Feb 2008 07:57:00 -0600</pubDate>
    </item>
  </channel>
</rss>
