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

Re: Startup time

To: sumith.narayanan@gmail.com
Subject: Re: Startup time
From: Quanah Gibson-Mount <quanah@zimbra.com>
Date: Tue, 11 Sep 2007 08:09:10 -0700
Cc: openldap-software@openldap.org
Content-disposition: inline
In-reply-to: <Pine.SOC.4.64.0709110844210.766@toolbox.rutgers.edu>
References: <11c336660709101436n737e29e5pd95e4e5408052d7a@mail.gmail.com> <87lkbdph0y.fsf@magenta.l4b.de> <Pine.SOC.4.64.0709110844210.766@toolbox.rutgers.edu>

--On Tuesday, September 11, 2007 8:59 AM -0400 Aaron Richton <richton@nbcs.rutgers.edu> wrote:

It's almost certain that this configuration is inappropriate. You're
unlikely to get a decently tuned cache for a database that size in 32-bit
process space.

As for your "crashes," you're likely OOM running into the DN cache issues
previously discussed

http://www.openldap.org/lists/openldap-software/200708/msg00106.html

and you may find help with a 64-bit platform, OpenLDAP 2.4, or some
combination thereof.

I think it is a little premature for OpenLDAP 2.4, but definitely go 64-bit, do some tuning, and actually provide useful details. You don't note the OS either, but if it is Linux, you probably want to use something like tcmalloc instead of glibc for memory management as well.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration

References:
- Startup time
  - From: "Sumith Narayanan" <sumith.narayanan@gmail.com>
- Re: Startup time
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: Startup time
  - From: Aaron Richton <richton@nbcs.rutgers.edu>

Prev by Date: Re: Startup time
Next by Date: alock package is unstable
Index(es):
- Chronological
- Thread