3 ms·
This is Foundation DB's announcement they are doing full ACID databases with a 14.4M writes per second capability. That is insanely fast in the data base world.
by ChuckMcM 12y ago
This is Foundation DB's announcement they are doing full ACID databases with a 14.4M writes per second capability. That is insanely fast in the data base world. Running in AWS with 32 c3.8xlarge configured machines. So basically NSA level data base capability for $150/hr. But perhaps more interesting is that those same machines on the open market are about $225,000. That's two rack, one switch and a
transaction rate that lets you watch every purchase made at every Walmart store in the US, in real time. That is assuming the stats are correct[1], and it wouldn't even be sweating (14M customers a day vs 14M transactions per second). Insanely fast.
I wish I was an investor in them.
[1] http://www.statisticbrain.com/wal-mart-company-statistics/ http://www.statisticbrain.com/wal-mart-company-statistics/
- vilda 12y agoNot all ACID transactions are equal. This is just a key-value store-like test. It shows the potential to scale, yet nothing regarding performance in real word. 32 c3.2xlarge instances have 1920GB memory. Given 1 billion 16B+ 8..100B values the whole dataset fits just into memory. The Cassandra test mentioned [1] sustained loss of 1/3 instances. That's very impressive! Would love to see how F-DB handles this type of real-life situation (hint hint for follow up blog post). [1] http://googlecloudplatform.blogspot.cz/2014/03/cassandra-hits-one-million-writes-per-second-on-google-compute-engine.html http://googlecloudplatform.blogspot.cz/2014/03/cassandra-hit...
- jbergens 12y agoThey do seem to talk about writes per second. That means you must flush to disk, not read from cache. [Edit, more info] They seem to run with multiple clients which also stresses the system. From their explanation * The clients simulate 320,000 concurrent sessions