[Date Prev][Date Next]
Re: LMDB file size, again
- To: Christian Sell <firstname.lastname@example.org>, "OpenLDAP, Technical" <email@example.com>
- Subject: Re: LMDB file size, again
- From: Howard Chu <firstname.lastname@example.org>
- Date: Fri, 13 Nov 2015 13:48:06 +0000
- In-reply-to: <1150425436.1142655.1447282266961.JavaMail.email@example.com>
- References: <58074298.1083910.1447266044431.JavaMail.firstname.lastname@example.org> <5643B86D.email@example.com> <1150425436.1142655.1447282266961.JavaMail.firstname.lastname@example.org>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38a1
Christian Sell wrote:
You're being stupid.
let's say I am stubborn. As I mentioned, I have the requirement that the user be
able to copy the database file away on their USB stick (or send it via email,
for that matter). With SQLite, that is no problem. But with LMDB under Windows
the user is looking at a huge file, which will be unacceptable in all
likelihood. I also must allow the user to copy using file system tools, and not
some custom utility.
So I take it that LMDB is simply not designed or suitable for such a scenario.
Windows and its lack of reasonable sparse file support makes it not a suitable
OS. (Windows supports sparse files, but not by default, and there is a 30%
performance degradation when using that support in LMDB.)
If you're stuck with Windows and these other requirements then I recommend you
use something other than LMDB, it is not appropriate for your use case.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/