[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: auto-growing data size
- To: openldap-technical@openldap.org
- Subject: Re: auto-growing data size
- From: mark diener <rpzrpzrpz@gmail.com>
- Date: Wed, 11 Apr 2018 18:08:15 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=wYrAggB2sw4iwU4apKwOD9AQIVyrAQJuQzrsCH92BHE=; b=ChiXdjtpBdKtRaqr7WBjLefkifrSFLxsB24sBwYwbvpOGqJ4GsCvFRFRyhldpeUoZI cI6TLeZpEPynUrhFapL08DCiMf9UN5hmGSRDqwjCHIC930SwRuZvjch+jB1OjUCdnNuz xyJv/Lv+yiaBcd5VffQmU/472zDXTrz5+xjHZxh7TsWxwk69wq8Qfwq8/Jxildn80+0V CfbyfuLwrOvav2WSIQui0YBakic57F+imToxRVeqRDif1wY+k0oGbyvTN3gLP9U0buQm 1sTqEaoy6Fs2p4cUA+IX2syrFxhQdWTKGF2NQfEu79v04spZN/yk5ErW461HEUmYmakI Kryw==
- In-reply-to: <CAChgv6qpFJtZ5GpC1si_dtbUqPtGw7Fv0r9s7U4zHa8=9gXRcA@mail.gmail.com>
- References: <CAChgv6qpFJtZ5GpC1si_dtbUqPtGw7Fv0r9s7U4zHa8=9gXRcA@mail.gmail.com>
I came across a python write up about lmdb:
http://lmdb.readthedocs.io/en/release/#environment-class
map_size:
Maximum size database may grow to; used to size the memory mapping. If
database grows larger than map_size, an exception will be raised and
the user must close and reopen Environment. 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 <rpzrpzrpz@gmail.com> wrote:
> 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 upper limit, not preallocate the space on storage.
>
> There are various areas in the documentation where it talks about
> having the database not grow without bounds.
>
> Comments?
>
>
> Marco