From: Hallvard Furuseth <hallvard@openldap.org>
Date: Tue, 12 Jan 2016 22:18:06 +0000 (+0100)
Subject: lmdb.h Caveats: Reserved vs. actual mem/disk usage
X-Git-Tag: LMDB_0.9.19~38
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=c2f6f04dba9006935bb89b5f0d08102e2776a4ab;p=openldap

lmdb.h Caveats: Reserved vs. actual mem/disk usage
---

diff --git a/libraries/liblmdb/lmdb.h b/libraries/liblmdb/lmdb.h
index c4d05d1791..14a05462a3 100644
--- a/libraries/liblmdb/lmdb.h
+++ b/libraries/liblmdb/lmdb.h
@@ -77,6 +77,11 @@
  *	  access to locks and lock file. Exceptions: On read-only filesystems
  *	  or with the #MDB_NOLOCK flag described under #mdb_env_open().
  *
+ *	- An LMDB configuration will often reserve considerable \b unused
+ *	  memory address space and maybe file size for future growth.
+ *	  This does not use actual memory or disk space, but users may need
+ *	  to understand the difference so they won't be scared off.
+ *
  *	- By default, in versions before 0.9.10, unused portions of the data
  *	  file might receive garbage data from memory freed by other code.
  *	  (This does not happen when using the #MDB_WRITEMAP flag.) As of