<?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:52:12 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Brian Moon's Blog: Apache Worker and PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/9641</guid>
      <link>http://www.phpdeveloper.org/news/9641</link>
      <description><![CDATA[<p>
In a <a href="http://doughboy.wordpress.com/2008/02/13/apache-worker-and-php/">recent post</a> to his blog, <i>Brian Moon</i> talks about the experience he's had with using PHP on Apache 2 with a <a href="http://www.php.net/manual/en/faq.installation.php#faq.installation.apache2">threaded MPM</a> at Dealnews.com.
</p>
<blockquote>
Well, first, what is an MPM? It stands for Multi-Processing Module. [...] The most commonly used threaded MPM is the Worker MPM. In this MPM, you have several processes that run multiple threads within it. This is the one I will be talking about.
</blockquote>
<p>
He <a href="http://doughboy.wordpress.com/2008/02/13/apache-worker-and-php/">goes on</a> to describe the "huge memory savings" that using the module got them - using the worker process to increase the child capacity of the Apache instance. He recommends keeping it simple when compiling a server to work with the worker functionality and mentions  how it can also help with serving static pages right along side the dynamic ones (without a second server!).
</p>
<p>
Check out <a href="http://doughboy.wordpress.com/2008/02/13/apache-worker-and-php/">the post</a> for a few more tips.
</p>]]></description>
      <pubDate>Fri, 15 Feb 2008 08:43:00 -0600</pubDate>
    </item>
  </channel>
</rss>
