Closed AskAlexSharov closed 3 years ago
When you define a geometry, the engine has no other way besides to apply it by following the appropriate steps (i.e. create a 64 Mb database file).
So I can advise advise such options:
/dev/shm
or /var/run
;Make sense - will try you mr advises next week.
We using LMDB with NoMetaSync|NoSync options - to run small app tests which need small (<64Mb) fast db (0 safety requirements).
LMDB in this configuration doesn't really touching disk much (probably until OS doesn't start evicting page cache).
Same tests on mdbx with mdbx.NoMetaSync | mdbx.UtterlyNoSync and 64Mb growth step geometry - 10 times slower than same tests on lmdb.
I think it happening because more intensive/earlier disk touches or because geometry taking place immediately.
( this issue is absolutely less important than https://github.com/erthink/libmdbx/issues/164 )