<?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>Sun, 07 Sep 2008 09:45:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Turland's Blog: Log Analysis and PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/8580</guid>
      <link>http://www.phpdeveloper.org/news/8580</link>
      <description><![CDATA[<p>
In a <a href="http://ishouldbecoding.com/2007/09/03/log-analysis-and-php/">new post</a>, <i>Matthew Turland</i> looks at one thing that he feels is missing from a lot of the PHP functionality currently available in the community today - log analysis features.
</p>
<blockquote>
Log analysis is a fairly common task in the field of web development, most often analysis of web server traffic logs or what Wikipedia refers to as <a href="http://en.wikipedia.org/wiki/Web_analytics">web analytics</a>. PHP has no officially supported extensions designed specifically for log analysis. There are no related extensions in PECL. The only remotely related extension in PEAR is <a href="http://pear.php.net/package/Log">PEAR_Log</a>, which for generating logs rather than parsing or analyzing them. In short, there is no common solution here.
</blockquote>
<p>
He looks at the options that developers do have - make their own solution or go with a third party option. <a href="http://ishouldbecoding.com/2007/09/03/log-analysis-and-php/">He believes</a>, though, that a PECL extension would be more the way to go, integrating with PHP more closely and allow for easier parsing and manipulating of the data in their own log files.
</p>]]></description>
      <pubDate>Mon, 03 Sep 2007 21:41:28 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Drupal.org: Tuning your server for optimal Drupal performance]]></title>
      <guid>http://www.phpdeveloper.org/news/5204</guid>
      <link>http://www.phpdeveloper.org/news/5204</link>
      <description><![CDATA[<p>
On the Drupal site, there's a <a href="http://drupal.org/node/2601">handy article</a> instructing you on getting the most performance out of your server for the <a href="http://drupal.org/">Drupal</a> software.
</p>
<quote>
<i>
The performance of your Drupal site is dependent on three main factors: the goals of your site, the resource demands of your site traffic, and the system performance and configuration of underlying technologies.
</i>
</quote>
<p>
They <a href="http://drupal.org/node/2601">seperate it out</a> into three different sections - setting out your performance goals, analysing your site for current traffic/resource consumption, and the actual implementation of the performance settings. They give a few steps here to follow to check what your server is currently using and some links to other tips on tuning the various pieces of the puzzle.
</p>
<p>
One thing that they mention that's worth repeating to any and all web developers out there: "Apache is bandwidth limited, PHP is CPU limited, and MySQL is memory limited and disk I/O bound".
</p>]]></description>
      <pubDate>Wed, 19 Apr 2006 07:14:14 -0500</pubDate>
    </item>
  </channel>
</rss>
