<?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>Tue, 08 Jul 2008 23:39:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Doug Brown's Blog: Zend_Cache is Saving me Money!]]></title>
      <guid>http://www.phpdeveloper.org/news/10543</guid>
      <link>http://www.phpdeveloper.org/news/10543</link>
      <description><![CDATA[<p>
<i>Doug Brown</i> has <a href="http://www.brownphp.com/2008/07/zend_cache-is-saving-me-money/">posted a new entry</a> to his blog about how the Zend_Cache component of the Zend Framework has saved him some money.
</p>
<p>
He and his site were taken offline by his own hosting company because of one little detail - the limit on usage for the shared server was 3% and his site was using 30%. Going through his logs, he found the culprit - a "too many connections" message from MySQL due to the number of requests.
</p>
<blockquote>
I'll admit, I was in a huge hurry to get this project done, so I wasn't thinking about the long term effects.  Needless to say, I wasn't caching my MySQL query results. I know, tisk tisk.
</blockquote>
<p>
He added a new private method to his class (using Zend_Cache to store the date) and dropped the call into his controller to pulled the cached info whenever it needed it.
</p>]]></description>
      <pubDate>Fri, 04 Jul 2008 07:55:01 -0500</pubDate>
    </item>
  </channel>
</rss>
