2 ms·
Serving up thousands of requests per seconds from 3 TB (while continually adding and updating more data!) is a lot different from just archiving it. A _lot_. :
by jbellis 17y ago
Serving up thousands of requests per seconds from 3 TB (while continually adding and updating more data!) is a lot different from just archiving it.
A _lot_. :)
To put it in perspective, 100GB is pretty much the limit of what you can serve from a single mysql machine, for instance. This will vary depending on exact workload but that is a reasonable ball park number.
- SwellJoe 17y agoOf course, in a relational database you wouldn't (generally) be storing the vast majority of the data in question...you'd be querying for it. That's not to trivialize the improvement in performance here, just to point out that this probably would be 100GB in a MySQL database.
- ntoshev 17y agoAny idea how much per machine can you serve when you use a bigtable/cassandra/dynamo/pnuts-like system instead of MySQL?
- ntoshev 17y agohttp://wiki.apache.org/cassandra/PoweredBy http://wiki.apache.org/cassandra/PoweredBy 330GB per machine for Facebook's Cassandra cluster.