3 ms·

RAM FS + fsync off?

• viraptor 6y ago
  Those solutions still have a high overhead. There's acid compliance, serialisation in memory, maintaining indices, and many other layers. Compare it to an ideal testing solution with no initialisation cost and insert being literally: parse the query, add a new entry to a list, done.
  • RantyDave 6y ago
    But you want to be testing against something that is as close as possible to the deployment environment. So if that means acid, indices etc, then that's what it is.
    • viraptor 6y ago
      You can still do them in a trivial way that works like production. For example: if some column has a unique index, look at all rows and compare the new value. You don't need an actual index for it. (And definitely not a fancy concurrent access btree) For transactions/mvcc you can literally make a copy of everything.
  • Avamander 6y ago
    Have you tried postgresql with libeatmydata?