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

Re: OpenLDAP DB_CONFIG values for a big Server

To: openldap-technical@openldap.org
Subject: Re: OpenLDAP DB_CONFIG values for a big Server
From: Emmanuel Lecharny <elecharny@gmail.com>
Date: Fri, 12 Mar 2010 16:35:53 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=URT3VHjj6HCavBM3+yr25aNIRG3fI5m52F855UAdrdU=; b=sK36Rc/cZnAQlrn6TmBrZ/N4phyU0bO+NzChPnWHmlhfNN+xbUv56qGOX84ixef56t zrzGcag+zAb3N0Qol+A6Z0BTKa38H4GR0k6QAsLb49nTcBzCrYrS3ja7CmkZ8PSjJ6pA xEw4ntDZ+oRcuNMKm6lNdbL6263Zj9F92iGhM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=twQBRzpXaAJXXLBhCWmsoFboXg1stROJalve5WjJaPjD80TKGKHYPQG7q4T6x9W+xb ADzBD73ZZJIKu9fhhLipdTWlv638sik9BF59QSvEfb2D34aqb0qYlTVfn2E+aF7Z0o5q xefUTOrDX8YiuHFXkBpZOLQ7kX+/u2vhIibro=
In-reply-to: <f9a50dce1003120633m569188d3m580f1ac375b13549@mail.gmail.com>
References: <f9a50dce1003120224x64cb0429r5aaac4d2305c3652@mail.gmail.com> <87pr39ivw9.fsf@rubin.avci.de> <f9a50dce1003120427p2544d14dg15d5db15846a26c5@mail.gmail.com> <87hboliss2.fsf@rubin.avci.de> <f9a50dce1003120633m569188d3m580f1ac375b13549@mail.gmail.com>
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3

On 3/12/10 3:33 PM, Echedey Lorenzo wrote:

Nice tricks,

I have specified an index for my filter search. Populating entries again to
take care of it.

No need to inject the entries again. You can re-index the base using the CL

Regarding shm_key, I have a couple of silly questions:

- I should create a shared memory region. Could you please point me in the
right direction? I've been googling but found nothing regarding creating it
and OpenLDAP
- I am afraid not all the database will fit in a shared memory region. The
machine has 16GB RAM and I think all the entries would be about ~22GB. What
may happend if it comes to grow and surpass the limit?

I would seriously suggest that you conduct some tests with all the indexsets, and then check if you get the expected performance, before doingsome extended tunning. Without running a perf test on the base, anytunning is like shouting in the dark ....


At least, define a baseline, and then do tune/perftest/compare loops.

You can use some tool like slamd for perf tests.

--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com

References:
- OpenLDAP DB_CONFIG values for a big Server
  - From: Echedey Lorenzo <echedey@gmail.com>
- Re: OpenLDAP DB_CONFIG values for a big Server
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: OpenLDAP DB_CONFIG values for a big Server
  - From: Echedey Lorenzo <echedey@gmail.com>
- Re: OpenLDAP DB_CONFIG values for a big Server
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: OpenLDAP DB_CONFIG values for a big Server
  - From: Echedey Lorenzo <echedey@gmail.com>

Prev by Date: Re: OpenLDAP DB_CONFIG values for a big Server
Next by Date: Re: OpenLDAP DB_CONFIG values for a big Server
Index(es):
- Chronological
- Thread