3 ms·
I just want to echo mike above with a slightly different tact that perhaps will get across my perception of our feelings. It's dishonest, at the very least, to
by merlincorey 14y ago
I just want to echo mike above with a slightly different tact that perhaps will get across my perception of our feelings.
It's dishonest, at the very least, to claim ACID compliance and then do benchmarks against a known ACID compliant competitor without having the same level of ACIDity enabled in your program.
If you want to prove how fast MemSQL is against MongoDB, that's one thing (I understand it also can be "fully durable" but it is not by default due to speed concerns). To prove how fast MemSQL is against MySQL, you have to prove it on the same playing field, which means it has to, necessarily, be just as ACIDic and respond to "real" queries on large datasets with high concurrency.
tl;dr Do some benchmarks of apples-to-apples ACID, and do something about the common case of a head of a table, then you will be honestly faster (or not) than MySQL
- pork 14y ago> (I understand it also can be "fully durable" but it is not by default due to speed concerns) Just a little addendum: MongoDB has been "durable by default" since v1.7 I believe (current: 2.0.6).
- jhugg 14y agoSince 2.0, the journal is enabled. It flushes to disk every 100ms. Operations can return successfully without writing the data to disk. This is similar to what MemSQL is offering by default.