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

Re: cn=monitor and timing?

To: Quanah Gibson-Mount <quanah@zimbra.com>
Subject: Re: cn=monitor and timing?
From: Dagobert Michelsen <dam@baltic-online.de>
Date: Sat, 25 Aug 2007 14:04:08 +0200
Cc: openldap-devel@openldap.org
In-reply-to: <E54B1D7D48499B5D022B6A94@[192.168.1.3]>
References: <E54B1D7D48499B5D022B6A94@[192.168.1.3]>

Hello Quanah,

Am 24.08.2007 um 21:57 schrieb Quanah Gibson-Mount:

I was wondering if it would be possible in cn=monitor to track the average time it takes slapd to respond to different operations, like ADD, MOD, SEARCH, DELETE. This could provide some useful information on server performance (although full-DB searches would of course add a bit of time to averages. :P ). Maybe something like top does -- Track the 1, 5, and 15 minute averages or something.

I have some experimental D-Trace support for this kind of measurements which is however limited to Solaris Nevada and maybe Solaris 10 U4 due to the need to instrument static functions. The difficult part here is choosing the neuralgic places in the code between whose measurements is most useful.


Best regards

  -- Dagobert

References:
- cn=monitor and timing?
  - From: Quanah Gibson-Mount <quanah@zimbra.com>

Prev by Date: Ignoring no-ops changes?
Next by Date: dynamic group caching (was: slapo-dynlist search member=value search?)
Index(es):
- Chronological
- Thread