<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>notJim</author><text>Slightly OT, but Tumblr gave a great talk about their sharding architecture here: &lt;a href=&quot;http://engineering.tumblr.com/post/12652551894/slides-from-our-velocity-europe-talk-on-mysql-sharding&quot; rel=&quot;nofollow&quot;&gt;http://engineering.tumblr.com/post/12652551894/slides-from-o...&lt;/a&gt;.&lt;p&gt;It&apos;s really quite a good intro to the subject, I think.</text><parent_chain></parent_chain></comment><story><title>Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs</title><url>http://engineering.tumblr.com/post/24612921290/jetpants-a-toolkit-for-huge-mysql-topologies</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ErrantX</author><text>This is excellent stuff; it fits a niggling problem I have (i.e. I&apos;m a better programmer than sysadmin, so managing massive data shards is a pain)&lt;p&gt;It&apos;s an elegant implementation. From a ~30 minute read through I reckon I can use it to replace our current &quot;hacked up&quot; solution in just a few hours.&lt;p&gt;Kudos Tumblr.</text><parent_chain></parent_chain></comment><story><title>Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs</title><url>http://engineering.tumblr.com/post/24612921290/jetpants-a-toolkit-for-huge-mysql-topologies</url></story>