RE: FW: OpenLDAP as an enterprise level LDAP provider (try II)

["Fortin, John {PBG}" <John.Fortin@pepsi.com>]

Quanah, here you go, in order:

	1) Doing the initial slapdd with indexing on never completed  We
ended up turning off indexing just to load the initial ldif file.  We then
ran slapindex after enabling the indexes.
	2) Dell 2650, dual 2.1 GHz Intel Zeon processors with Hyperthreading
support, 2 Gig Ram, 76 Gig HD with Raid 5.  
	3) As I indicated, hot backups are not possible due to the
slapadd/slapindex issues.  If I can make this perform better then I can do
it.
      4)DB_CONFIG during load:	
		set_cachesize   0      52428800        0
		set_lg_regionmax        1048576
		set_lg_max              10485760
		set_lg_bsize            1097152
		set_lg_dir              /var/ldapdb/slave2/logs
		set_tmp_dir             /tmp
		set_flags DB_LOG_AUTOREMOVE

I'm tryin to make this work.  I'm surprised at the results too.  If I'm not
tuning this properly, I can adjust.  These were values suggested in one of
the links in the FAQ, though I did increase set_cachesize.

I do vaguely remember someone complaining about performance on RedHat, but I
cannot find the reference in the archives.

Thanks!!
--John

John Fortin
PBG Middleware and Web Services
(914) 767-7844


>-----Original Message-----
>From: Quanah Gibson-Mount [mailto:quanah@stanford.edu] 
>Sent: Wednesday, November 24, 2004 3:34 PM
>To: Fortin, John {PBG}; OpenLDAP-software@OpenLDAP.org
>Subject: Re: FW: OpenLDAP as an enterprise level LDAP provider (try II)
>
>
>John,
>
>You really need something that formats your email better.
>
>First some notes:
>
>slapadd indexes while adding the DB.
>
>First, There is no reason to index *after* slapadd-ing, you 
>are wasting 
>your time.
>
>Second, you don't say what hardware platform you are using and 
>what the 
>memory/disk resources are.  OpenLDAP (and all directory 
>services from what 
>I can tell) is bounded by memory and disk.  You need plenty of both.
>
>Third, as I recall, you can hot backup BDB starting with the 
>4.2 branch.  I 
>personally use the slapcat option.
>
>Fourth, you do not say what BDB flags you enable/disable when 
>slapadding. 
>This can greatly impact your slapadd time.
>
>Fifth, you do not say how large you configured your BDB DB 
>Cache to be. 
>This can greatly impact your slapadd time.
>
>Finally, I'll note that it took me 16 minutes to slapadd (with 
>indexing) a 
>large 500k entry DB on a Dual CPU Dell 1750 with 2GB of RAM.  
>2GB of RAM 
>was not sufficient however, to hold the DB in memory as well 
>as run slapd. 
>I'd guestimate the system would truly need 4GB of RAM for that.
>
>Regards,
>Quanah