3 ms·
I don't think they're avoiding Cassandra as their tweet store because it's not capable of performing well. It's probably more cause it would be a really long pr
by alex1 16y ago
I don't think they're avoiding Cassandra as their tweet store because it's not capable of performing well. It's probably more cause it would be a really long process migrating every tweet into Cassandra. I'm sure if they could, they would go back to the first day Twitter launched, and use Cassandra as the tweets store.
As for query time, maybe your problem was I/O throughput? I've read Cassandra can be really slow if you have poor I/O throughput. This happens a lot in the cloud, where I/O is usually shared.
- jacobbijani 16y agoDon't they not show / hide & archive old tweets anyway? Seems like they could really simple transition Cassandra in if they wanted to.
- mrduncan 16y agoOn a small scale, yes. On Twitter scale (in February they were averaging 50 million tweets/day [1]), it's probably not so simple. [1] http://blog.twitter.com/2010/02/measuring-tweets.html http://blog.twitter.com/2010/02/measuring-tweets.html Edit: As of mid June, it was about 65 million per day. http://blog.twitter.com/2010/06/big-goals-big-game-big-records.html http://blog.twitter.com/2010/06/big-goals-big-game-big-recor...
- jacobbijani 16y agoMy point was that they aren't importing legacy data at all if they aren't showing old stuff. Just start writing the new ones to the new DB, right?