mimblewimble team mailing list archive

[Luke Kenneth Casson Leighton <lkcl@xxxxxxxx>]

a couple other things: 1 lmdb is specifically designed for efficiency
(optimised for read because it's for use in openldap).  that *happens*
to accidentally result in fast write performance under certain
commonly-occurring [but *not* all] circumstances.  2 if you use
compression on the values (i'd recommend snappy as it's a very fast
partial-compression algorithm) whilst you gain on a reduced storage
size you _will_ lose the speed benefits of not having that memcpy copy
the value (like on every other key-value store), you would have to do
decompress on every single value before you could access it.

l.