sharing DB_ENV between DB berkeleydb instances

Caolán McNamara <caolanm -AT- redhat.com>

Fri, 23 Mar 2012 16:42:42 +0000

Digging into our memory usage, I see that we have 6 berkeleydb DBs, all of which are opened with a NULL DB_ENV argument which makes berkeleydb create an internal one for each, which adds up to a substantial chunk of memory. On the face of it at least it seems to be legal to share a single DB_ENV among the lot, i.e. like so... http://cgit.freedesktop.org/libreoffice/core/commit/?id=76876513479522b37c9047a418521624e27afff6 Anyone know if this is a really bad idea :-) C.

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.