Issue 5178 - [feature request] pcache stats & monitoring
Summary: [feature request] pcache stats & monitoring
Status: RESOLVED PARTIAL
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-09 13:20 UTC by ando@openldap.org
Modified: 2014-08-01 21:05 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description ando@openldap.org 2007-10-09 13:20:07 UTC
Full_Name: Pierangelo Masarati
Version: HEAD/re24
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (193.203.230.29)
Submitted by: ando


This is a feature request for stats and monitoring capabilities for pcache;
basically:

- the number of cached queries
- the number of cached entries
- possibly, a list of cached queries in cachedQueryURL form
- how many times each cached query was used instead of re-running the request
- the ratio answerable / cacheable for each cacheable query
- some global figure like the average response time (send searchResult time -
start caching time) for each query, and the overall average.

Adding per-query info could be done by either extending the cachedQueryURL
format or by adding a child entry for each cached query (like connections and
other dynamic info).

p.

Comment 1 ando@openldap.org 2007-10-09 14:06:42 UTC
changed notes
moved from Incoming to Software Enhancements
Comment 2 ando@openldap.org 2009-08-17 21:30:22 UTC
> This is a feature request for stats and monitoring capabilities for
> pcache;
> basically:
>
> - the number of cached queries

The number of cachedQueryURL values

> - the number of cached entries

not available; maybe cachedQueryURL could carry a x-nentries=<num> extension

> - possibly, a list of cached queries in cachedQueryURL form

ditto

> - how many times each cached query was used instead of re-running the
> request
> - the ratio answerable / cacheable for each cacheable query
> - some global figure like the average response time (send searchResult
> time -
> start caching time) for each query, and the overall average.

None of the above is available.  The first one is interesting, but it
would require query information to survive its life, and match by
base/scope/filter rather than by queryUUID.

> Adding per-query info could be done by either extending the cachedQueryURL
> format or by adding a child entry for each cached query (like connections
> and
> other dynamic info).

This second option does not seem to be viable, although interesting.  I
fear too much overhead.

It's not clear yet how all of this stuff will need to cooperate with the
new TTR (and bind caching, when available).

p.

Comment 3 ando@openldap.org 2009-08-17 22:07:20 UTC
changed notes
changed state Open to Partial
moved from Software Enhancements to Development
Comment 4 ando@openldap.org 2009-08-19 21:10:25 UTC
changed notes
Comment 5 OpenLDAP project 2014-08-01 21:05:00 UTC
infrastructure added to HEAD;
cachedQueryURL, pcacheNumQueries, pcacheNumEntries exposed in HEAD