<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Crazy&#039;s Blog &#187; performance</title>
	<atom:link href="http://blog.crazytje.be/tag/performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crazytje.be</link>
	<description></description>
	<lastBuildDate>Sun, 28 Aug 2011 13:37:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Using APC to store your data</title>
		<link>http://blog.crazytje.be/using-apc-to-store-your-data/</link>
		<comments>http://blog.crazytje.be/using-apc-to-store-your-data/#comments</comments>
		<pubDate>Tue, 31 Aug 2010 15:14:56 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[APC]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[apc]]></category>
		<category><![CDATA[opcode caching]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=387</guid>
		<description><![CDATA[Sometimes you have large amount of generated data that you don’t want to create on every web request. An examples would be a home page with several news posts on it. The text would be in a database, but all the ‘extra’ things you did like bbtags present in the text, information about the user <a href='http://blog.crazytje.be/using-apc-to-store-your-data/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/using-apc-to-store-your-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing your web server: Part 4b – XDebug Profiler</title>
		<link>http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/</link>
		<comments>http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 20:21:08 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[profile]]></category>
		<category><![CDATA[xdebug]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=297</guid>
		<description><![CDATA[Here we are, part 4b. By using XDebug, a pecl extension, our php code can be analyzed pinpointing the slower functions. Installing XDebug is easy: pecl install xdebug Now, you&#8217;ll have to enable it in the php.ini file: extension=xdebug.so xdebug.profiler_enable=1 xdebug.profiler_output_name=profiler-%s-%t.cache xdebug.profiler_output_dir=/tmp/xdebug Don&#8217;t forget to create the directory and give apache enough permissions to write <a href='http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing your web server: Part 4a – PHP</title>
		<link>http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/</link>
		<comments>http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 20:15:35 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=236</guid>
		<description><![CDATA[Let me start by saying, I won&#8217;t bore you with the list of what I call stupid optimizations. That&#8217;s why I call this 4a, I recommend skipping 4a and go directly to 4b When I first when on my quest to optimize my code, I was disappointed at what I found. Let me give you <a href='http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing your web server: Part 2 &#8211; Keep Alives</title>
		<link>http://blog.crazytje.be/optimizing-your-web-server-part-2-keep-alives/</link>
		<comments>http://blog.crazytje.be/optimizing-your-web-server-part-2-keep-alives/#comments</comments>
		<pubDate>Sun, 22 Nov 2009 16:18:57 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=227</guid>
		<description><![CDATA[Once your site begins to grow, it will most likely contain dozens of images, css and js files, and many other requests. Keep alives allows those requests to happen over the same tcp/ip connection. So what is keep alive exactly? As mentioned before, keep alive is an option in the apache config, this was added <a href='http://blog.crazytje.be/optimizing-your-web-server-part-2-keep-alives/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/optimizing-your-web-server-part-2-keep-alives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

