[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
LMDB: file size increase (due to new free pages) even though write transaction does not add/update items
- To: openldap-technical@openldap.org
- Subject: LMDB: file size increase (due to new free pages) even though write transaction does not add/update items
- From: Argyrios Kyrtzidis <akyrtzi@gmail.com>
- Date: Fri, 1 Apr 2016 00:47:24 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=JTL5ITR0F7kMCT+yKWWD8ryZI5s0rOQkVMl20biSlA8=; b=YOHoPT3KORdCzuC+uCBgBHtGbU9nZ2yqenV9m6qlWGYzSwkt+tMPx06FIGL71iaCoe i+tnJltRAY4hvTkLoLOktCGQ98yIGZaRteMkIv0kM2lvKmYQ7sUmyMmg+daMeg59jGuT tukj22ue8zFXLE0EE+CqiadDxFQbI7FM/NZie1Gt5NvnAst0SJrB/q7Jp0ExvYoqZS5B ZdM7BGmQolXbnbaRuIy7vDn5Mln6GrwhIMecqTHkijwpvc1gEs3sDow2kudsgS1UzhIW Eu8ACCPL0mUYOYk445pnBTDHKvld0FbBupgbWidyXrdq1RCKTeMjQBjS2yijWplCwAYC kQGA==
Hi,
Thank you for making LMDB available.
I’m using LMDB on OSX (without MDB_WRITEMAP, so the database file size is relative to the stored data, not the max mapsize).
I’ve noticed that write transactions that have a large number of ‘attempted’ updates, but that do not actually make any updates due to MDB_NOOVERWRITE / MDB_NODUPDATA, cause an increase in the database file size, which mdb_stat attributes to an increased number of free pages.
This is with latest master of the github mirror.
I’m wondering if you have any hints on what I may be doing wrong ? I’d like if possible to avoid the database size increasing if the write pass did not make any updates.