<?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/"
		>
<channel>
	<title>Comments on: WordPress 3.0 Memory Requirements: 256 MB</title>
	<atom:link href="http://alexrabe.de/2010/07/05/wordpress-3-0-memory-requirements-256-mb/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexrabe.de/2010/07/05/wordpress-3-0-memory-requirements-256-mb/</link>
	<description>ALEX RABE &#124; learning by doing...</description>
	<lastBuildDate>Thu, 17 May 2012 09:30:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Rajeev Jha</title>
		<link>http://alexrabe.de/2010/07/05/wordpress-3-0-memory-requirements-256-mb/#comment-22691</link>
		<dc:creator>Rajeev Jha</dc:creator>
		<pubDate>Thu, 01 Dec 2011 06:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://alexrabe.de/?p=674#comment-22691</guid>
		<description>I believe this is pretty sneaky from wordpress team to change php.ini settings inside an application. I did a 3.2.1 install and saw my 256MB slice thrash - Just plain install (w/o plugins) and one post. I tried changing the MAX_MEMORY_LIMIT to 32MB/48MB but that also did not work. swap continued unabated.

I switched back to 2.9.2 and everything is running happy on same 256MB slice. I can understand that loading more features may require more RAM but base install memory requirements should not change. Also, the fact that PHP settings are being tampered with should be highlighted in bold red on install.</description>
		<content:encoded><![CDATA[<p>I believe this is pretty sneaky from wordpress team to change php.ini settings inside an application. I did a 3.2.1 install and saw my 256MB slice thrash &#8211; Just plain install (w/o plugins) and one post. I tried changing the MAX_MEMORY_LIMIT to 32MB/48MB but that also did not work. swap continued unabated.</p>
<p>I switched back to 2.9.2 and everything is running happy on same 256MB slice. I can understand that loading more features may require more RAM but base install memory requirements should not change. Also, the fact that PHP settings are being tampered with should be highlighted in bold red on install.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raven</title>
		<link>http://alexrabe.de/2010/07/05/wordpress-3-0-memory-requirements-256-mb/#comment-21421</link>
		<dc:creator>Raven</dc:creator>
		<pubDate>Fri, 06 Aug 2010 17:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://alexrabe.de/?p=674#comment-21421</guid>
		<description>Well, i&#039;m already with 128M and i think it&#039;s a lot of memory too</description>
		<content:encoded><![CDATA[<p>Well, i&#8217;m already with 128M and i think it&#8217;s a lot of memory too</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HG</title>
		<link>http://alexrabe.de/2010/07/05/wordpress-3-0-memory-requirements-256-mb/#comment-21382</link>
		<dc:creator>HG</dc:creator>
		<pubDate>Wed, 21 Jul 2010 22:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://alexrabe.de/?p=674#comment-21382</guid>
		<description>Get major issues with nextgen gallery. 

otherwise ok, I hope most of you edited your php.ini file.</description>
		<content:encoded><![CDATA[<p>Get major issues with nextgen gallery. </p>
<p>otherwise ok, I hope most of you edited your php.ini file.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

