Even faster: loading half a billion rows in MySQL revisited
derwiki.tumblr.com
derwiki.tumblr.com
MySQL Partitioning: this was the most similar to our existing set up, since MySQL internally stores the data into different tables. We decided against it because it seemed likely that it wouldn’t be much faster than our current solution (although MySQL can internally do some optimizations to make sure you only look at tables that could possibly have data you want). And it’s still the same complexity we were looking to reduce (and would further be the only database set up in our system using partitioning).
(Your comment about automatic/transparent makes me think you're probably thinking of merge tables. We've used those too for other models, but we're not big fans of them because they require you to use the MyISAM storage engine, which doesn't offer the same consistency guarantees that InnoDB does.)
In this particular instance, a single large table with the right indices gives better performance and, importantly for us, speeds up developers by removing unnecessary complexity.