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

Re: server startup overhead

To: Eric Irrgang <erici@motown.cc.utexas.edu>
Subject: Re: server startup overhead
From: Howard Chu <hyc@symas.com>
Date: Fri, 25 May 2007 18:51:56 -0700
Cc: openldap-software@openldap.org
In-reply-to: <Pine.LNX.4.64.0705252009250.31229@valen.cc.utexas.edu>
References: <Pine.LNX.4.64.0705251414320.31229@valen.cc.utexas.edu> <46576859.6080104@symas.com> <Pine.LNX.4.64.0705251929450.31229@valen.cc.utexas.edu> <Pine.LNX.4.64.0705252009250.31229@valen.cc.utexas.edu>
User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.9a5pre) Gecko/20070523 SeaMonkey/1.5a

Eric Irrgang wrote:

Is there a way (with or without attaching a debugger) to find out what my IDL cache and DN cache is doing?

Using a debugger, set a breakpoint inside any of the backend functions. When the bdb pointer is set up, print out its data. The bdb->bi_cache structure records all the info about the entry cache. The bdb->bi_idl_* fields records the info about the IDL cache. In 2.4 some of these counters are exposed via back-monitor. We can add more to the monitor entry as needed.

--
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP     http://www.openldap.org/project/

Follow-Ups:
- Re: server startup overhead
  - From: "Gabriel Stein" <gabrielstein@gmail.com>

References:
- server startup overhead
  - From: Eric Irrgang <erici@motown.cc.utexas.edu>
- Re: server startup overhead
  - From: Howard Chu <hyc@symas.com>
- Re: server startup overhead
  - From: Eric Irrgang <erici@motown.cc.utexas.edu>
- Re: server startup overhead
  - From: Eric Irrgang <erici@motown.cc.utexas.edu>

Prev by Date: Re: server startup overhead
Next by Date: Re: referential integrity
Index(es):
- Chronological
- Thread