I\'m working with a huge table which has 250+ million rows. The schema is simple.
CREATE TABLE MyTable (
id BIGINT PRIMARY KEY AUTO_INCREMENT,
From my experience with Innodb it seems to hit a limit for write intensive systems even if you have a really optimized disk subsystem. I am surprised you managed to get it up to 100GB.
This is what twitter hit into a while ago and realized it needed to shard - see http://github.com/twitter/gizzard.
This all depends on your use cases but you could also move from mysql to cassandra as it performs really well for write intensive applications.(http://cassandra.apache.org)