<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: More on WPMU Performance</title>
	<atom:link href="http://itmoves.wordpress.com/2008/10/26/more-on-wpmu-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://itmoves.wordpress.com/2008/10/26/more-on-wpmu-performance/</link>
	<description>Adventures In Teaching and Technology</description>
	<lastBuildDate>Wed, 16 Dec 2009 06:17:32 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Chun</title>
		<link>http://itmoves.wordpress.com/2008/10/26/more-on-wpmu-performance/#comment-488</link>
		<dc:creator>Ben Chun</dc:creator>
		<pubDate>Sun, 09 Nov 2008 18:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://itmoves.wordpress.com/?p=243#comment-488</guid>
		<description>The thing that actually fixed our performance problems was setting a MaxRequestsPerChild in Apache&#039;s mpm.conf -- which is really just a hack that restarts each child process after serving a certain number of requests.  We have it set at 1000 right now, and it solved our problems.

This means that somewhere WordPress is either leaking memory or hanging or holding a database connection open or... I don&#039;t know.  It doesn&#039;t make much sense.  I suppose PHP or MySQL could also be at fault, but we didn&#039;t see these problems until after upgrading from WPMU 1.3 to 2.6 so that&#039;s at least part of the issue.  It could just be that there&#039;s code now that exercises parts of PHP or MySQL that were not previously used, and they are leaking or otherwise at fault.</description>
		<content:encoded><![CDATA[<p>The thing that actually fixed our performance problems was setting a MaxRequestsPerChild in Apache&#8217;s mpm.conf &#8212; which is really just a hack that restarts each child process after serving a certain number of requests.  We have it set at 1000 right now, and it solved our problems.</p>
<p>This means that somewhere WordPress is either leaking memory or hanging or holding a database connection open or&#8230; I don&#8217;t know.  It doesn&#8217;t make much sense.  I suppose PHP or MySQL could also be at fault, but we didn&#8217;t see these problems until after upgrading from WPMU 1.3 to 2.6 so that&#8217;s at least part of the issue.  It could just be that there&#8217;s code now that exercises parts of PHP or MySQL that were not previously used, and they are leaking or otherwise at fault.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elad Salomons</title>
		<link>http://itmoves.wordpress.com/2008/10/26/more-on-wpmu-performance/#comment-458</link>
		<dc:creator>Elad Salomons</dc:creator>
		<pubDate>Sun, 26 Oct 2008 21:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://itmoves.wordpress.com/?p=243#comment-458</guid>
		<description>Hi,
Thank you for updating &lt;a href=&quot;http://www.ringofblogs.com/2008/01/17/using-wp-super-cache-plugin-with-wordpress-mu&quot; rel=&quot;nofollow&quot;&gt;my solution&lt;/a&gt; for the cache issue.
As for S3, check out my plugin for &lt;a href=&quot;http://www.ringofblogs.com/2008/04/12/off-loading-wpmu-theme-files-to-amazon-s3/&quot; rel=&quot;nofollow&quot;&gt;offloading theme files to Amazon S3&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Thank you for updating <a href="http://www.ringofblogs.com/2008/01/17/using-wp-super-cache-plugin-with-wordpress-mu" rel="nofollow">my solution</a> for the cache issue.<br />
As for S3, check out my plugin for <a href="http://www.ringofblogs.com/2008/04/12/off-loading-wpmu-theme-files-to-amazon-s3/" rel="nofollow">offloading theme files to Amazon S3</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
