This content has been marked as final. Show 4 replies
Hi,1 person found this helpful
this is strange behaviour, since the cache Hit Ratio is a percentage value showing the ratio of results taken from the cache vs the number of total requests.
Moreover, it's strange the you're running a 'plain' DS5.2-Patch5, since it was a bad patch and NEED to have at least an hot-fix on top of it to keep it running.
1. Which is exactly the output of:
# cd <DS5.2_INSTALL_ROOT>/bin/slapd/server/64
# ./ns-slapd -D <DS_INSTANCE_DIRECTORY> -V
2. Exactly of which DB cache hit ratio are you talking about? Entry cache usage? Indexes? Entry access? The one split by suffix or the TOTAL?
Thanks for reply Marco.
--As per your comment, version of the Directory Server is
Sun Microsystems, Inc.
Sun Java(TM) System Directory Server/5.2_Patch_5 B2007.093.0058
However we have palns for version upgradation.
-- It is the TOTAL of all entry and index.
I observed that toal value of hits is not matching with individual entry access and index.
Hmmm, sounds a bit strange, but have you summed the values for ALL the indexes, or are you considering only the first index (generally 'aci')?
Maybe you are hitting this bug we hit in 6.3. We were told it is fixed in 22.214.171.124
12270511 N/A DIRECTORY 6.3 MONITORING PRODID-8512 PORTID-453 12244450 SUNBT2177955 DBCACHEHITRATIO SOMETIMES EXCEEDS 100 PERCENT
DB cache hits and miss counter can wrap around (start over at zero) thereby leading to incorrect cache hit ratio calculations.