[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: 2.1.17 performance issues

To: openldap-software@OpenLDAP.org
Subject: Re: 2.1.17 performance issues
From: Andreas <andreas@conectiva.com.br>
Date: Wed, 23 Apr 2003 18:32:23 -0300
Content-disposition: inline
In-reply-to: <00b201c309de$3609afa0$0e01a8c0@CELLO>
References: <20030423205154.GT32589@conectiva.com.br> <00b201c309de$3609afa0$0e01a8c0@CELLO>
User-agent: Mutt/1.5.4i

On Wed, Apr 23, 2003 at 02:20:38PM -0700, Howard Chu wrote:
> Andreas is correct. back-bdb maintains its own entry cache separately from
> whatever caching the BDB library itself uses. In very early OpenLDAP 2.1 code
> there was no entry cache for back-bdb because we believed that the BDB
> library's caching would be "good enough" but subsequent benchmarking showed
> that an entry cache was needed.

So, configuring this parameter in slapd.conf *and* a cache in DB_CONFIG will cause
two caches to be used, one in openldap and the other in the bdb library?

Follow-Ups:
- RE: 2.1.17 performance issues
  - From: "Howard Chu" <hyc@highlandsun.com>

References:
- Re: 2.1.17 performance issues
  - From: Andreas <andreas@conectiva.com.br>
- RE: 2.1.17 performance issues
  - From: "Howard Chu" <hyc@highlandsun.com>

Prev by Date: RE: 2.1.17 performance issues
Next by Date: LDIF and structural objectclasses
Index(es):
- Chronological
- Thread