9:24 a.m.
Is anyone aware of any buggy in openldap+bdb related to memory usage?
Have anyone here using this type of backend ? Any problem to report?
Thanks for your time and cooperation.
Best regards.
10:02 a.m.
--On Thursday, November 01, 2012 2:24 PM -0200 Friedrich Locke
<friedrich.locke(a)gmail.com> wrote:
Is anyone aware of any buggy in openldap+bdb related to memory
usage?
Have anyone here using this type of backend ? Any problem to report?
No. Yes. No.
I would suggest you provide some more detailed information as to what, if
any, problem you feel you are experiencing. This email is quite vague.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
10:02 a.m.
01.11.2012 20:24, Friedrich Locke пишет:
Is anyone aware of any buggy in openldap+bdb related to memory
usage?
Have anyone here using this type of backend ? Any problem to report?
It's leaking. I think. Needs regular restart.
slapd-2.4.23+libdb-4.8.30
slapd-git-a54957b+libdb-4.8.30
--
WBR,
Roman Rybalko
10:34 a.m.
--On Thursday, November 01, 2012 9:02 PM +0400 Roman Rybalko
<openldap(a)romanr.name> wrote:
01.11.2012 20:24, Friedrich Locke пишет:
> Is anyone aware of any buggy in openldap+bdb related to memory usage?
> Have anyone here using this type of backend ? Any problem to report?
It's leaking. I think. Needs regular restart.
slapd-2.4.23+libdb-4.8.30
slapd-git-a54957b+libdb-4.8.30
Again, you have provided no real useful information. I've used
back-bdb/hbd for over a decade across openldap 2.1, 2.2, 2.3, and 2.4, with
databases of significant size. No memory leak.
Of course, if you use glibc instead of a decent memory allocator like
tcmalloc, you may see behavior where glibc leaks like a sieve.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
10:17 a.m.
Roman Rybalko wrote:
01.11.2012 21:34, Quanah Gibson-Mount пишет:
> Of course, if you use glibc instead of a decent memory allocator like
> tcmalloc, you may see behavior where glibc leaks like a sieve.
Yep, I use glibc, let me try tcmalloc, will report if it leaks, thanks!
Maybe it's not really a leak what you're seeing.
See Howard's presentation slide 16 ff. you can download here:
http://www.openldap.org/conf/odd-tuebingen-2006/
Ciao, Michael.
5:05 p.m.
Roman Rybalko wrote:
01.11.2012 20:24, Friedrich Locke пишет:
> Is anyone aware of any buggy in openldap+bdb related to memory usage?
> Have anyone here using this type of backend ? Any problem to report?
It's leaking. I think. Needs regular restart.
slapd-2.4.23+libdb-4.8.30
slapd-git-a54957b+libdb-4.8.30
If you can show concrete evidence of a leak, please file an ITS with your
configuration, sample workload, and the memory leak report. (E.g. from
valgrind, tcmalloc leak check, or some other memory tracking tool.)
I routinely test with valgrind and tcmalloc, and have not seen any memory
leaks in back-bdb/hdb in many years.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
10:02 a.m.
On 11/01/2012 05:24 PM, Friedrich Locke wrote:
Is anyone aware of any buggy in openldap+bdb related to memory
usage?
Have anyone here using this type of backend ? Any problem to report?
I guess it would help others if you mentioned the OpenLDAP version you
are referring to. Did check the changes and issue tracker?
http://www.openldap.org/software/release/changes.html
http://www.openldap.org/its/
Regards,
Patrick
4046
days inactive
4047
days old
openldap-technical@openldap.org
7 comments
6 participants
participants (6)
-
Friedrich Locke -
Howard Chu -
Michael Ströder -
Patrick Lists -
Quanah Gibson-Mount -
Roman Rybalko