<?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>Krishnendu&#039;s Blog</title>
	<atom:link href="http://www.krishnendu.com/feed" rel="self" type="application/rss+xml" />
	<link>http://www.krishnendu.com</link>
	<description>Few of My Thoughts and Me ...</description>
	<lastBuildDate>Mon, 16 Jan 2012 04:57:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>MySQL &#8211; Which Database Engine to Choose</title>
		<link>http://www.krishnendu.com/mysql-which-database-engine-to-choose_15.html</link>
		<comments>http://www.krishnendu.com/mysql-which-database-engine-to-choose_15.html#comments</comments>
		<pubDate>Sat, 14 Jan 2012 17:53:40 +0000</pubDate>
		<dc:creator>Krish</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Cache]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[Computing]]></category>
		<category><![CDATA[Data management]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[MyISAM]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Archive]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[web applications]]></category>
		<category><![CDATA[Web Server]]></category>

		<guid isPermaLink="false">http://www.krishnendu.com/?p=15</guid>
		<description><![CDATA[Few days back for an application development by my team, I needed to research on this. Problem was we have 8 million places zip code, the data is updated 3 times per day &#8211; but it&#8217;s not working fast enough, and sometimes even the kernel fails at the of update. I found it is using InnoDB engine by default. MyISAM offers speed whereas Innodb offers reliability. MyISAM is fast but with no transactions support, Innodb has certain, but very important limitations. If there are many modifications of the data, it&#8217;s said that InnoDB works faster because it uses row locking instead of table locking, like MyISAM. However, if there are mainly SELECT statements, a MyISAM table might be faster. If there are many modifications of the data, it&#8217;s said that InnoDB works faster because it uses row locking instead of table locking, like MyISAM. My suggestion &#8211; for concurrent inserts and updates, one should go for data integrity rather than speed. &#160; &#160; Use Case 1 ================ InnoDB for most of the tables, including the messaging (short e-mails back and forth) because we need the row-level locking (memory page level locking, really. That&#8217;s important when you have so many updates per second like we do.) MyISAM (packed, preferably) for static data &#8212; UK zip code info is over 120M unpacked, and it never changes (and if it does, we just replace the table). Use Case 2 ================= For reliability and performance, we use InnoDB for almost everything at Wikipedia &#8211; we just can&#8217;t afford the downtime implied by MyISAM use and check table for 400GB of data when we get a crash. The speed advantage of MyISAM is overstated IMO. LiveJournal with a mostly write environment saw a big increase in speed when it switched from MyISAM to InnoDB and they are very happy with InnoDB. At Wikipedia we achieved some major performance gains by exploiting the way InnoDB clusters records by their primary key. Took some quite common queries from 50 seeks per result page to 1 or 2 seeks per page. Worse, the code at that time allowed people to go back 50,000 rows using LIMIT, causing 50,000 seeks and a DOS vulnerability. Big improvement to working set size from the change as well, so the results were more often in cache. It&#8217;s so great an advantage that like the write caching it could be a dealbreaker for [...]]]></description>
		<wfw:commentRss>http://www.krishnendu.com/mysql-which-database-engine-to-choose_15.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rebooting Fresh &#8230;..</title>
		<link>http://www.krishnendu.com/rebooting-fresh_9.html</link>
		<comments>http://www.krishnendu.com/rebooting-fresh_9.html#comments</comments>
		<pubDate>Mon, 09 Jan 2012 08:49:35 +0000</pubDate>
		<dc:creator>Krish</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[krishnendu]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[web applications]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.krishnendu.com/?p=9</guid>
		<description><![CDATA[After deleting my all old installation of WordPress and loosing all of my posting Data &#8211; starting fresh with a fresh new wordpress, new theme and new ideas in mind. I almost lost all my old posts. So, will concentrate on latest topics which can be helpful for my old readers. If anyone have any special post request &#8211; you are free to contact me anytime.]]></description>
		<wfw:commentRss>http://www.krishnendu.com/rebooting-fresh_9.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

