2 ms·
There is a reason they are fast. They didn't use to have durability. Think about that -- it is a database product that until the last version didn't have durabi
by rdtsc 15y ago
There is a reason they are fast. They didn't use to have durability. Think about that -- it is a database product that until the last version didn't have durability and its writes were not acknowledged with a response. If you store you data in memory and write it to disk sometimes, you can write very fast.
- latch 15y agoand now, since 2 versions, they have journaling, and offer a huge amount of flexibility over write durability available: - fire and forget - write with integrity check (safe) - write with journal commit - write with data file commit - write with replication to X nodes And you can combine the last 4 in any way you like. They did a pretty good job turning a downside into a significant advantage (yes, fire and forget is a significant advantage in a lot of cases).
- rdtsc 15y ago> and now, since 2 versions So 20-30 days ago only? > yes, fire and forget is a significant advantage in a lot of cases Sorry, but not as a default option in a DATAbase product.
- deleted 15y ago[deleted]