id investigate re-design if possible to shard out the high potential load by default, unless you rea
id investigate re-design if possible to shard out the high potential load by default, unless you really really need one table to potentially eat up 10gb on its own, there is a good chance you can treat all user accounts the same and shard out the high potential, or expire / purge old data you don't need in the OLTP store. Doing lookups and joins later with rows 1-x on one shard and 1,000,000-y on another will be problematic.
