Equation 1: Estimate Size of Database Cache
dbcachesize = SUM(allDB4files)
Note: Equation 1 gives you a very rough estimation for dbcachesize. When estimating database cache size, include only those database (db4) files that your operations need. For 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, see the
Figure 2 shows performance results using the
Figure 2: Performance based on
operations/sec
20000 |
|
|
|
|
|
18000 |
|
|
|
|
|
16000 |
|
|
|
|
|
14000 |
|
|
|
|
|
12000 |
|
|
|
|
|
10000 |
|
|
|
|
|
8000 |
|
|
|
| 250k, 2 |
6000 |
|
|
|
|
|
4000 |
|
|
|
|
|
2000 |
|
|
|
|
|
0 |
|
|
|
|
|
0 | 100 | 200 | 300 | 400 | 500 |
dbcache in 1000000 bytes
The
This performance tuning attribute specifies the cache size in terms of available memory space. The simplest method is limiting cache size in terms of memory occupied. Activating automatic cache resizing overrides this attribute, replacing these values with its own guessed values at a later stage of the server startup. Attempting to set a value that is not a number or is too big for a
8