From users-return-4483-apmail-directory-users-archive=directory.apache.org@directory.apache.org Thu Mar 1 09:01:41 2012 Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A000C95BE for ; Thu, 1 Mar 2012 09:01:41 +0000 (UTC) Received: (qmail 95990 invoked by uid 500); 1 Mar 2012 09:01:41 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 95919 invoked by uid 500); 1 Mar 2012 09:01:40 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 95909 invoked by uid 99); 1 Mar 2012 09:01:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2012 09:01:40 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.210.178 as permitted sender) Received: from [209.85.210.178] (HELO mail-iy0-f178.google.com) (209.85.210.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2012 09:01:35 +0000 Received: by iakl21 with SMTP id l21so713810iak.37 for ; Thu, 01 Mar 2012 01:01:15 -0800 (PST) Received-SPF: pass (google.com: domain of ayyagarikiran@gmail.com designates 10.50.85.202 as permitted sender) client-ip=10.50.85.202; Authentication-Results: mr.google.com; spf=pass (google.com: domain of ayyagarikiran@gmail.com designates 10.50.85.202 as permitted sender) smtp.mail=ayyagarikiran@gmail.com; dkim=pass header.i=ayyagarikiran@gmail.com Received: from mr.google.com ([10.50.85.202]) by 10.50.85.202 with SMTP id j10mr10050748igz.58.1330592475496 (num_hops = 1); Thu, 01 Mar 2012 01:01:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=CdGRWVECY2kDcfzb8OsJ7H2GBHYu2AIOxa5UbvthuG0=; b=Dt4IiT1QHfF494OCl7zIV8L5EdctPoTyufbdRdy8Y1xlsZTPlDMq5xsp3BImr8gV55 +B5rkojU142L9SfZtKsDbt948I+bPwk+TRdx6d1XLajBQ66oAZAA1WDtYPzrPSsnmJrR Yb9IU2r6WtUxslBOm6ImDZW5vo1f4431YdAW4= MIME-Version: 1.0 Received: by 10.50.85.202 with SMTP id j10mr8314452igz.58.1330592475444; Thu, 01 Mar 2012 01:01:15 -0800 (PST) Sender: ayyagarikiran@gmail.com Received: by 10.42.166.68 with HTTP; Thu, 1 Mar 2012 01:01:15 -0800 (PST) In-Reply-To: <4F4F13D0.8020503@gmail.com> References: <2BE7E81B77921F43A6A273C2DF2FA6A43C0F571387@IBSMBX.ibs-ag.com> <4F4F13D0.8020503@gmail.com> Date: Thu, 1 Mar 2012 14:31:15 +0530 X-Google-Sender-Auth: VKOnCx1i7ugRUnIjRX9euZ1DEFg Message-ID: Subject: Re: Quesiton about best way to index attributes From: Kiran Ayyagari To: users@directory.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Mar 1, 2012 at 11:44 AM, Emmanuel L=E9charny = wrote: > Le 2/29/12 7:50 PM, Kiran Ayyagari a =E9crit : > >> On Wed, Feb 29, 2012 at 11:44 PM, =A0wrote: >>> >>> Hi, We have =A0apacheds 2.0-M5 db setup with all =A0~90k users under on= e OU. >>> Yes, I know they should be stored with some hierarchy but that's not an >>> option for this >>> particular customer. > > Having 90K users in one single OU is *not* a bad practice. You may want t= o > setup a hierarchy, but this is not mandatory. > > >>> =A0I want to optimize searching by lastname, (sn), firstname (givenName= ) >>> and displayName. I have created indexes under the partition and >>> we see ads-indexcachesize is set by default to 100. Assuming the value >>> correlates to a value for the attribute, =A0Can I set this to 50,000 fo= r each >>> of the attribs?. >> >> that won't help much, setting up more memory for the JVM will help > > You still can increase the number to a higher value, but you must know th= at > as soon as the higher BTree pages will be loaded, the speedup will be low= er. > With 100 pages loaded, you have most of the BTree loaded. > > If you have enough memory, just increase this value to 50 000, should not > harm. > > > In any case, I would suggest that once you have increased those values fo= r > each index that you do a full search to load all of them in memory, to ch= eck > that you don't get an OOM, before running in production. > >> >> Also, is there a way to rebuild the indexes in 2.0? I can't seem to find >> how that's done. >> >> no, one way is to delete the index and restart the server followed by >> adding the index and restart, then the server will automatically build >> the index >> during startup > > Kiran : haven't we added some utility tool to do that ? (It's a bit far i= n > the past.. If we don't have them, we must add them) > yes, I have added but was not maintained after that > I'm wondering if we don't have a JIRA for that... > AFAIR there is one for generic tooling > -- > Regards, > Cordialement, > Emmanuel L=E9charny > www.iktek.com > --=20 Kiran Ayyagari