RE: Problem loading 100K entries into OpenLDAP2.2.24

["Mavric Domen ITWEN5" <d.mavric@iskratel.si>]

Hi,

I've tested also 2.2.24 release with patches suggested by 
Mr. Chu. Now, automatic removal of log files works as expected and
consumption of memory is not increasing so quickly. I configured now slapd.conf to take about 120MB of RAM. The memory is not released after loading and the total consumption of memory (all processes)increases from 200MB to 600MB (of 1GB). When loading the next portion of 100K entries, total memory grows to 900MB (of 1GB), slapd takes 130MB.
Is it normal that memory is not released after loading, even after
performing checkpoints, and cleaning log files?

Thanks, BR, 
Domen


-----Original Message-----
From: 罗志坚 [mailto:luozhijian@huawei.com] 
Sent: Thursday, April 21, 2005 4:22 AM
To: openldap-software@OpenLDAP.org
Subject: Fw: Problem loading 100K entries into OpenLDAP2.2.24


> > Mavric Domen ITWEN5 wrote:
> > 
> > >  Hello,
> > >
> > >  I've performed some tests with 2.3.2 beta release and in general it
> > >  works better, slapd stays alive, but it still takes about 200 MB of
> > >  memory and it does NOT free it after the loading.
> > 
> > That is normal; you can reduce the entry cachesize in slapd.conf if you 
> > want it to keep less memory.
> I think it is strange!!
> After loading,
> free memory reduce size = data file size
> And the size have relation with slapd.conf,only affected by data file size.
> Even restart slapd,the free memory size didn't increase.

sorry,It's "the size have no relation with slapd.conf,only affected by data file size",not "the size have relation with slapd.conf,only affected by data file size"

> 
> > 
> > >  Also the log files are still not removed after the checkpoints, this
> > >  is also the case when doing manual checkpoint and "db_archive -d".
> > >  There are 104 log files in DB_HOME directory, each of 10MB. The only
> > >  way to clear the logs is to shutdown the server.
> > >
> > >  What else I should check? I've run out of ideas to solve this
> > >  problem.
> > 
> > You need an additional patch to BerkeleyDB and to back-bdb. The 
> > BerkeleyDB patch is here
> > 
> > http://www.openldap.org/devel/cvsweb.cgi/build/BerkeleyDB42.patch
> > 
> > and the back-bdb patch is in CVS HEAD, back-bdb/cache.c.
> > 
> > The BerkeleyDB patch file will be distributed in the next 2.3 beta 
> > release, and the back-bdb patch will of course be present as well.
> > 
> > -- 
> >   -- Howard Chu
> >   Chief Architect, Symas Corp.       Director, Highland Sun
> >   http://www.symas.com               http://highlandsun.com/hyc
> >   Symas: Premier OpenSource Development and Support
> >