<?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>Sat, 25 May 2013 04:30:18 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Brandon Savage's Blog: Scaling Up: Reducing Drag, Increasing Lift]]></title>
      <guid>http://www.phpdeveloper.org/news/12014</guid>
      <link>http://www.phpdeveloper.org/news/12014</link>
      <description><![CDATA[<p>
<i>Brandon Savage</i> has posted <a href="http://www.brandonsavage.net/scaling-up-reducing-drag-increasing-lift/">the next article</a> in his "Scaling Up" series, a look at reducing the amount of "drag" your application makes through its processing path and some tips to help increase its "lift" out of some common problems.
</p>
<blockquote>
The intuitive will note that many if not most of these suggestions are performance enhancements, not scaling techniques. Why then are they in an series about scaling? Scaling is about more than just adding hardware. It's also about making sure your system runs better. You can add lots and lots of hardware but you will someday be unable to compensate for bad queries and poor optimization.
</blockquote>
<p>
Some of his suggestions include taking care of any sort of errors or notices (anything that could slow the script down by writing to a log), defining virtual hosts instead of making excessive use of .htaccess files and installing caching software to maximize code and information reuse.
</p>]]></description>
      <pubDate>Tue, 24 Feb 2009 15:13:15 -0600</pubDate>
    </item>
  </channel>
</rss>
