<story><title>Loading half a billion rows into MySQL</title><url>http://derwiki.tumblr.com/post/24490758395/loading-half-a-billion-rows-into-mysql</url></story><parent_chain></parent_chain><comment><author>alexatkeplar</author><text>Assuming your event data is immutable (i.e. no UPDATEs, just INSERTs), you&apos;d probably have fewer headaches long-term if you just dumped the database to flatfiles, stored in HDFS and queried using Hive (which has MySQLish query syntax anyway). This architecture will take you to billions of rows quite happily.&lt;p&gt;This is the architecture we use for eventstream analysis at SnowPlow (&lt;a href=&quot;https://github.com/snowplow/snowplow&quot; rel=&quot;nofollow&quot;&gt;https://github.com/snowplow/snowplow&lt;/a&gt;).</text></comment>
<story><title>Loading half a billion rows into MySQL</title><url>http://derwiki.tumblr.com/post/24490758395/loading-half-a-billion-rows-into-mysql</url></story><parent_chain></parent_chain><comment><author>whalesalad</author><text>I want to give this 10 upvotes. This is one of those things you only see on HN occasionally, and it&apos;s full of all kinds of awesome little nuggets. That command to get the count from the information_schema in and of itself is gold (I now know about the tee command)</text></comment>