<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>Venu Anuganti Blog</title>
	
	<link>http://venublog.com</link>
	<description>Everything In Life Is Random! (Personal and Work)</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:59:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/venublog/apQq" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="venublog/apqq" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>MySQL At Scale – Zynga Games</title>
		<link>http://venublog.com/2010/12/02/mysql-at-scale-zynga-games/</link>
		<comments>http://venublog.com/2010/12/02/mysql-at-scale-zynga-games/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 03:51:48 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[NoSQL]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Scalability]]></category>
		<category><![CDATA[Zynga]]></category>
		<category><![CDATA[How to scale games]]></category>
		<category><![CDATA[membase at Zynga]]></category>
		<category><![CDATA[MySQL at Zynga]]></category>
		<category><![CDATA[Zynga Games Scale]]></category>
		<category><![CDATA[Zynga membase]]></category>
		<category><![CDATA[Zynga mysql]]></category>
		<category><![CDATA[Zynga Performance]]></category>
		<category><![CDATA[Zynga Scalability]]></category>
		<category><![CDATA[Zynga Scale]]></category>
		<category><![CDATA[Zyngaa At Scale]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/12/02/mysql-at-scale-zynga-games/</guid>
		<description><![CDATA[Recently am part of Zynga&#8216;s database team as I was pretty much impressed with company&#8217;s database usage. As everyone knows how popular Zynga games like Farmville, Cafe World, Mafia Wars, Poker, FrontierVille, FishVille, PetVille and Treasure Island etc are. Zynga launched yet another new game today called CityVille along with series of acquisitions (latest today [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/12/02/mysql-at-scale-zynga-games/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Why Kickfire is a fail in MySQL Data warehouse</title>
		<link>http://venublog.com/2010/08/04/why-kickfire-is-a-fail-in-mysql-data-warehouse/</link>
		<comments>http://venublog.com/2010/08/04/why-kickfire-is-a-fail-in-mysql-data-warehouse/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 23:28:08 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Data Warehouse]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[NoSQL]]></category>
		<category><![CDATA[Scalability]]></category>
		<category><![CDATA[Kickfire]]></category>
		<category><![CDATA[MySQL Data warehouse]]></category>
		<category><![CDATA[OLAP appliance]]></category>

		<guid isPermaLink="false">http://venublog.com/?p=684</guid>
		<description><![CDATA[Even though Data warehouse is picking very rapidly in the last year or so, but few companies who are already made a right mark in the right time could not take the market share that easily due to number of reasons. Even though am not a marketing guy to go over, but some of the [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/08/04/why-kickfire-is-a-fail-in-mysql-data-warehouse/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>MapReduce – DBInputFormat – Serialization on readers</title>
		<link>http://venublog.com/2010/07/19/mapreduce-dbinputformat-serilization-on-readers/</link>
		<comments>http://venublog.com/2010/07/19/mapreduce-dbinputformat-serilization-on-readers/#comments</comments>
		<pubDate>Tue, 20 Jul 2010 05:46:46 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Cloudera]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Hadopp]]></category>
		<category><![CDATA[Mapreduce]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Scalability]]></category>
		<category><![CDATA[cloudera import tool]]></category>
		<category><![CDATA[DBInputFomat Locking issue]]></category>
		<category><![CDATA[Hive]]></category>
		<category><![CDATA[how to load mysql data to hadoop]]></category>
		<category><![CDATA[mapreduce isolation]]></category>
		<category><![CDATA[Sqoop]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/07/19/mapreduce-dbinputformat-serilization-on-readers/</guid>
		<description><![CDATA[Last week I was working on EC2 MySQL server where one of the slave is taking lot of time to catch-up; and only job that is running on that server is mapreduce job to access InnoDB tables for read-only meta data. And debugging it further, noticed that every access to database server is serialized with [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/07/19/mapreduce-dbinputformat-serilization-on-readers/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Random Pauses In MySQL – File Handle Serialization</title>
		<link>http://venublog.com/2010/07/19/random-pauses-in-mysql-file-handle-serialization/</link>
		<comments>http://venublog.com/2010/07/19/random-pauses-in-mysql-file-handle-serialization/#comments</comments>
		<pubDate>Tue, 20 Jul 2010 03:36:38 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Scalability]]></category>
		<category><![CDATA[closing tables]]></category>
		<category><![CDATA[MySQL open tables performance]]></category>
		<category><![CDATA[opening tables]]></category>
		<category><![CDATA[table_cache]]></category>
		<category><![CDATA[table_open_cache]]></category>
		<category><![CDATA[THR_LOCK_open]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/07/19/random-pauses-in-mysql-file-handle-serialization/</guid>
		<description><![CDATA[Last month, I blogged about a case involving InnoDB, where all threads acting on InnoDB tables completely stuck for about few hours doing nothing; until we found a way to get around and make the threads to run and do the actual work. There are few more cases where the server can get into pause [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/07/19/random-pauses-in-mysql-file-handle-serialization/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>How read_buffer_size Impacts Write Buffering and Write Performance</title>
		<link>http://venublog.com/2010/06/23/how-read_buffer_size-impacts-write-buffering-and-write-performance/</link>
		<comments>http://venublog.com/2010/06/23/how-read_buffer_size-impacts-write-buffering-and-write-performance/#comments</comments>
		<pubDate>Wed, 23 Jun 2010 19:30:50 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Scalability]]></category>
		<category><![CDATA[mysql filesort performance]]></category>
		<category><![CDATA[mysql negative performance]]></category>
		<category><![CDATA[mysql OUTFILE performance]]></category>
		<category><![CDATA[mysql sequential IO buffering]]></category>
		<category><![CDATA[read_buffer_size]]></category>
		<category><![CDATA[tuning read_buffer_size]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/06/23/how-read_buffer_size-impacts-write-buffering-and-write-performance/</guid>
		<description><![CDATA[Even though the name read_buffer_size implies that the variable controls only read buffering, but it actually does dual purpose by providing sequential IO buffering for both reads and writes. In case of write buffering, it groups the sequential writes until read_buffer_size(it is min(read_buffer_size, 8K)); and then actually does the physical write once the buffer is [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/06/23/how-read_buffer_size-impacts-write-buffering-and-write-performance/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Autocommit, Implicit Commit and Open Transactions</title>
		<link>http://venublog.com/2010/06/12/autocommit-implicit-commit-and-open-transactions/</link>
		<comments>http://venublog.com/2010/06/12/autocommit-implicit-commit-and-open-transactions/#comments</comments>
		<pubDate>Sun, 13 Jun 2010 07:11:55 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[autocommit implicit commit]]></category>
		<category><![CDATA[autocommit open transaction]]></category>
		<category><![CDATA[Implicit commit]]></category>
		<category><![CDATA[MySQL active transaction error]]></category>
		<category><![CDATA[mysql fails to truncate table]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/06/12/autocommit-implicit-commits-and-open-transactions/</guid>
		<description><![CDATA[If you have any open transaction(s); and if there is any statement that causes implicit commit, especially DDL statements; then the current active transaction will be committed and transaction will be closed automatically. Here is the list of statements that causes implicit commit in MySQL. But other day; we had an issue in production as [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/06/12/autocommit-implicit-commit-and-open-transactions/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>InnoDB In a Complete Locked Mode</title>
		<link>http://venublog.com/2010/06/07/innodb-in-a-complete-locked-mode/</link>
		<comments>http://venublog.com/2010/06/07/innodb-in-a-complete-locked-mode/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 08:42:33 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[InnoDB hangs]]></category>
		<category><![CDATA[InnoDB locked]]></category>
		<category><![CDATA[innodb threads locked]]></category>
		<category><![CDATA[innodb_concurrency_tickets]]></category>
		<category><![CDATA[innodb_thread_concurrency]]></category>
		<category><![CDATA[MySQL-innodb]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/06/07/innodb-in-a-complete-locked-mode/</guid>
		<description><![CDATA[Today morning, we had a weird issue in one of the staging OLAP server (ETL); where all the InnoDB threads were locked and waiting on a signal condition for about 3-4 hours without performing any work related to InnoDB until we noticed it. Processlist indicates every thread is in ACTIVE state mode like Sending Data, [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/06/07/innodb-in-a-complete-locked-mode/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>MySQL Query Engine Scalability Issues</title>
		<link>http://venublog.com/2010/05/11/mysql-query-engine-scalability-issues/</link>
		<comments>http://venublog.com/2010/05/11/mysql-query-engine-scalability-issues/#comments</comments>
		<pubDate>Tue, 11 May 2010 08:27:32 +0000</pubDate>
		<dc:creator>Venu Anuganti</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Scalability]]></category>
		<category><![CDATA[mysql key cache contention]]></category>
		<category><![CDATA[mysql pending scalability issues]]></category>
		<category><![CDATA[mysql performance]]></category>
		<category><![CDATA[mysql query_cache performance]]></category>
		<category><![CDATA[MySQL Scalability]]></category>
		<category><![CDATA[mysql sort_buffer_size]]></category>
		<category><![CDATA[mysql table_cache]]></category>

		<guid isPermaLink="false">http://venublog.com/2010/05/11/mysql-query-engine-scalability-issues/</guid>
		<description><![CDATA[Lately in the MySQL community, we only hear about scalability or performance improvements of storage engines, but nothing about query engine itself. For example, one classic example being InnoDB; if we look back all the scalability issues that community reported a year back or even few months back; most part of those issues have been [...]]]></description>
		<wfw:commentRss>http://venublog.com/2010/05/11/mysql-query-engine-scalability-issues/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss><!-- Dynamic page generated in 0.647 seconds. --><!-- Cached page generated by WP-Super-Cache on 2012-02-02 08:59:40 -->

