This is only relevant for Windows. We use master branch which on Windows allocates disk space on demand, but is slower. For interactive applications allocating all space is inconvenient, but resizing env is even more inconvenient so we prefer on-demand allocation by default. Idea is that Windows is usually a dev machine and on Linux there is no performance overheads from on-demand allocations (LMDB just works that way there).
But e.g. on Windows Server (or big machine that acts like a server, or powerful workstation will a dedicated disk) one could afford pre-allocating hundreds of GBs.
This is only relevant for Windows. We use master branch which on Windows allocates disk space on demand, but is slower. For interactive applications allocating all space is inconvenient, but resizing env is even more inconvenient so we prefer on-demand allocation by default. Idea is that Windows is usually a dev machine and on Linux there is no performance overheads from on-demand allocations (LMDB just works that way there).
But e.g. on Windows Server (or big machine that acts like a server, or powerful workstation will a dedicated disk) one could afford pre-allocating hundreds of GBs.
Should name the package Spreads.LMDB.RE
See discussion in #19