sharing DB_ENV between DB berkeleydb instances
mstahl at redhat.com
Fri Mar 23 11:29:11 PDT 2012
On 23/03/12 17:42, Caolán McNamara wrote:
> 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...
> Anyone know if this is a really bad idea :-)
the Linux-RHEL6-x86_64 at 14-with-check tinderbox seems to think so:
> DB_THREAD mandates memory allocation flag on data DBT
> warn:legacy.osl:9258:1:/home/tinderbox/master/desktop/source/deployment/dp_persmap.cxx:63: [/home/tinderbox/master/workdir/unxlngx6/CustomTarget/smoketest/user/extensions/bundled/extensions.db] Berkeley Db error (0): Db::get: Invalid argument
> warn:legacy.osl:9258:1:/home/tinderbox/master/desktop/source/deployment/manager/dp_manager.cxx:1474: OSL_ASSERT
> Test name: N12_GLOBAL__N_14TestE::test
> equality assertion failed
> - Expected:
> - Actual : Extensions:install(Extension Install Extension)
> Failures !!!
> Run: 1 Failure total: 1 Failures: 1 Errors: 0
More information about the LibreOffice