<?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>blog's amazing &#187; performance</title>
	<atom:link href="http://blog.dotsamazing.com/category/performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dotsamazing.com</link>
	<description>web tech delicacies</description>
	<lastBuildDate>Wed, 04 May 2011 22:10:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>MySQL &#8211; limitations you never heard of</title>
		<link>http://blog.dotsamazing.com/2010/10/mysql-limitations-you-never-heard-of/</link>
		<comments>http://blog.dotsamazing.com/2010/10/mysql-limitations-you-never-heard-of/#comments</comments>
		<pubDate>Wed, 27 Oct 2010 10:13:29 +0000</pubDate>
		<dc:creator>d-a-m</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[databases]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[binary log]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[limitations]]></category>
		<category><![CDATA[single-threaded replication]]></category>
		<category><![CDATA[subqueries]]></category>

		<guid isPermaLink="false">http://blog.dotsamazing.com/?p=63</guid>
		<description><![CDATA[We all know MySQL has its limits &#8211; it works fine in general, but has its weaknesses too. The authors of MySQL Performance blog started a miniseries about such limitations for experienced users. Okay, I guess you know there&#8217;s no way to create fulltext index on InnoDB tables &#8211; but bid you know, that MySQL [...]]]></description>
		<wfw:commentRss>http://blog.dotsamazing.com/2010/10/mysql-limitations-you-never-heard-of/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HipHop for PHP &#8211; the buzz summary you should really read</title>
		<link>http://blog.dotsamazing.com/2010/02/hiphop-for-php-the-buzz-summary-you-should-really-read/</link>
		<comments>http://blog.dotsamazing.com/2010/02/hiphop-for-php-the-buzz-summary-you-should-really-read/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 11:18:35 +0000</pubDate>
		<dc:creator>d-a-m</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[emerging technologies]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://blog.dotsamazing.com/?p=55</guid>
		<description><![CDATA[HipHop for PHP from Facebook hit the streets several days ago resulting in dozens of posts about the technology. Let&#8217;s see what the PHP community says:

Marco Tabini enlists the HipHop features and encourages using it
the echolibre blog talks about possible security/buffer overflow implications, and mentions similar available solutions
Ilia Alshanetsky provides an excellent and thorough overview: [...]]]></description>
		<wfw:commentRss>http://blog.dotsamazing.com/2010/02/hiphop-for-php-the-buzz-summary-you-should-really-read/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Closure: How not to write JavaScript</title>
		<link>http://blog.dotsamazing.com/2009/11/google-closure-how-not-to-write-javascript/</link>
		<comments>http://blog.dotsamazing.com/2009/11/google-closure-how-not-to-write-javascript/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 11:06:43 +0000</pubDate>
		<dc:creator>d-a-m</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[emerging technologies]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[google closure]]></category>
		<category><![CDATA[HTML5 canvas]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[memory leak]]></category>
		<category><![CDATA[object]]></category>
		<category><![CDATA[optimization]]></category>
		<category><![CDATA[poor optimization]]></category>
		<category><![CDATA[prototype]]></category>
		<category><![CDATA[unoptimized]]></category>

		<guid isPermaLink="false">http://blog.dotsamazing.com/?p=49</guid>
		<description><![CDATA[Dmitry Baranovskiy, the creator of the Raphaël and gRaphaël JavaScript libraries has serious criticism against the Google Closure JS library.
According to Dmitry:

“It’s a JavaScript library written by Java developers who clearly don’t get JavaScript.”
poorly optimized loops and unoptimized switch statements
memory caching with unlimited size: “I’m not sure what this pattern is called in Java, but [...]]]></description>
		<wfw:commentRss>http://blog.dotsamazing.com/2009/11/google-closure-how-not-to-write-javascript/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>“Micro” Optimizations That Matter</title>
		<link>http://blog.dotsamazing.com/2009/10/%e2%80%9cmicro%e2%80%9d-optimizations-that-matter-brandonsavage-net/</link>
		<comments>http://blog.dotsamazing.com/2009/10/%e2%80%9cmicro%e2%80%9d-optimizations-that-matter-brandonsavage-net/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 09:21:59 +0000</pubDate>
		<dc:creator>d-a-m</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[autoloader]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[cdn]]></category>
		<category><![CDATA[content-delivery network]]></category>
		<category><![CDATA[error logging]]></category>
		<category><![CDATA[optimization]]></category>
		<category><![CDATA[output buffering]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[real-time data]]></category>

		<guid isPermaLink="false">http://blog.dotsamazing.com/?p=32</guid>
		<description><![CDATA[Brandon Savage compiled a good summary of application performance tips. Definitely not the difference between using single and double quotes in your code: these are easy to implement and effective (=&#8221;micro&#8221;) methods to improve responsiveness of your code, like:

Caching
Eliminate Any Sort Of Logged Errors
Enable Output Buffering For Everything
Make Use Of A Content-Delivery Network
Determine What Data [...]]]></description>
		<wfw:commentRss>http://blog.dotsamazing.com/2009/10/%e2%80%9cmicro%e2%80%9d-optimizations-that-matter-brandonsavage-net/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Watch out for your CRON jobs</title>
		<link>http://blog.dotsamazing.com/2009/10/watch-out-for-your-cron-jobs/</link>
		<comments>http://blog.dotsamazing.com/2009/10/watch-out-for-your-cron-jobs/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 10:59:56 +0000</pubDate>
		<dc:creator>d-a-m</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[background]]></category>
		<category><![CDATA[cron]]></category>
		<category><![CDATA[error handling]]></category>
		<category><![CDATA[exclusive]]></category>
		<category><![CDATA[job]]></category>
		<category><![CDATA[locking]]></category>
		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://blog.dotsamazing.com/?p=29</guid>
		<description><![CDATA[Running CRON jobs is not an easy task if you want to do it perfectly: fortunately we&#8217;re doing it similarly as it&#8217;s recommended by the Percona guys:
- prevent running multiple copies using file locks
- watch for errors
- store historical run times (use logging)
Further details and code sample in Watch out for your CRON jobs at [...]]]></description>
		<wfw:commentRss>http://blog.dotsamazing.com/2009/10/watch-out-for-your-cron-jobs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

