HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

Table 70 Database file-specific
Current totalPerformance metric
The number of times that a search result resulted in a cache hit on this specific
file. That is, a client performs a search that requires data from this file, and
the directory obtains the required data from the cache.
Cache Hits
The number of times that a search result failed to hit the cache on this specific
file. That is, a search that required data from this file was performed, and the
required data could not be found in the cache.
Cache Misses
The number of pages brought to the cache from this file.Pages Read In
The number of pages for this file written from cache to disk.Pages Written Out
14.6.2 Monitoring databases from the command line
The directory's database activities can be monitored using any LDAP too, such as ldapsearch,
using the following characteristics:
• Search with the attribute filter objectClass=*.
• Use the search base cn=monitor,cn=database_instance, cn=ldbm database,
cn=plugins, cn=config. database_instance is the name of the database to monitor.
• Use the search scope base.
For example:
ldapsearch -h directory.example.com -s base -p 389 -D "cn=Directory Manager" -w secret
-b "cn=monitor,cn=Example,cn=ldbm database,cn=plugins, cn=config" "objectclass=*"
In this example, the ldapsearch operation looks for the Example database. For information on
searching the directory, see “Using ldapsearch” (page 556).
Monitoring the server's activities shows the following information:
Table 71 Directory server monitoring attributes
DescriptionAttribute
Identifies the type of database currently being monitored.database
Indicates whether the database is in read-only mode; 0 means that the server
is not in read-only mode, 1 means that it is in read-only mode.
readonly
The total number of successful entry cache lookups. That is, the total number of
times the server could process a search request by obtaining data from the
cache rather than by going to disk.
entrycachehits
The total number of entry cache lookups since the directory was last started.
That is, the total number of search operations performed against the server
since server startup.
entrycachetries
Ratio that indicates the number of entry cache tries to successful entry cache
lookups. This number is based on the total lookups and hits since the directory
entrycachehitratio
was last started. The closer this value is to 100%, the better. Whenever a search
operation attempts to find an entry that is not present in the entry cache, the
directory has to perform a disk access to obtain the entry. Thus, as this ratio
drops towards zero, the number of disk accesses increases, and directory
search performance drops. To improve this ratio, increase the number of entries
that the directory maintains in the entry cache by increasing the value of the
Maximum Entries in Cache attribute. See “Tuning database performance” (page
539) for information on changing this value using the Directory Server Console.
The total size of directory entries currently present in the entry cache.currententrycachesize
The maximum number of directory entries that can be maintained in the entry
cache. This value is managed by the Maximum Entries in Cache setting. See
maxentrycachesize
14.6 Monitoring database activity 527