![](/images/backgrounds/286169/hp-hp-ux-red-hat-directory-server-software-white-paper-66972310x1.png)
Red Hat Directory Server 7.1 Performance Tuning and Sizing Guidelines
Step 2: Prime the directory by sending the following ldapsearch command (label it as ldapsearch command 1):
#./ldapsearch
Step 3: check db related monitoring attributes by sending a different ldapsearch request. (label it as ldapsearch command 2):
#./ldapsearch
dbcachehits: 236
dbcachetries: 280
dbcachehitratio: 84
dbcachepagein: 44
dbcachepageout: 0
dbcacheroevict: 0
dbcacherwevict: 0
•Step 4: If dbcachepageout, dbcacheroevict and dbcacherwevict are not equal to zero, you might want to increase
To estimate the amount of RAM needed for an optimized database cache, you can use the following formula:
Equation 1: Estimate Size of Database Cachedbcachesize = SUM(allDB4files)
•Please note: Equation 1 only gives you a very rough estimation for dbcachesize. When estimating database cache size, only the database (db4) files that your operations need should be included. As an example, if your directory server only needs to support exact search requests on the “cn” attribute, you may need just 354MB dbcache instead of 685MB dbcache which is the sum of all database (db4) files for the 250K databases. For more information about how to manage indexes, please refer to “Red Hat Directory Server 7.1 Administrator’s Guide”
Page 7