11 Nov
2015
11 Nov
'15
1:51 p.m.
Christian Sell wrote:
Hello, following up to my previous question regarding file size, I would like to ask about the recommended approach:
You're being stupid.
The documentation already clearly states: http://symas.com/mdb/doc/group__mdb.html#gaa2506ec8dab3d969b0e609cd82e619e5
The size of the memory map is also the maximum size of the database. The value should be chosen as large as possible, to accommodate future growth of the database.
- set a low file size initially, watch for MDB_MAP_FULL return codes and
increase the file/map size stepwise as needed
No. That would be stupid.
- choose a large file size and reduce the size by doing a mdb_copy when the
application shuts down
No. That would be stupid.
or maybe a combination of the two? How does SQLightning handle this (2. doesn't sound practical)?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/