need to switch to
> UFS, which supports sparse files like most other POSIX filesystems.
>
> Meanwhile - even if you're using HFS, you should still just set the map size
> to the largest value you ever expect to use. Preallocating the space will
> give better runtime performance, and will all
Anybody have any idea on how to have the database file
grow until you get to the mapsize instead of pre-allocating the entire
mapsize (4GB) upon initialization?
mdb_env_set_mapsize() ;
I don't mind having an upper limit on the map size, but I think it
would be helpful
to have it grow to the
. On 64-bit there is no
penalty for making this huge (say 1TB). Must be <2GB on 32-bit.
Well, it will be a penalty on MacOSX, it will create a 1TB file on
disk upon initialization!
What am I missing here?
Marco
On Wed, Apr 11, 2018 at 10:27 AM, mark diener <rpzrpz...@gmail.com> wrote:
