|
| Red Hat Directory Server 7.1 Performance Tuning and Sizing Guidelines | |
|
|
|
|
|
|
|
|
| Machine | Machine Specification | |
| Class |
|
|
| SD64B | Within partition one cell with 4 |
|
|
| as 8 1.6GHz CPUs, 64 GB memory, OS B.11.23 |
|
| Server: |
|
|
| Machine | Machine Specification |
|
| Class |
|
|
| SD64B | Within the partition one cell with 4 |
|
|
| counted as 8 1.6GHz CPUs, 128 GB memory, OS B.11.23 |
|
|
| List 2: Client and Sever machine specifications. | |
Appendix D: Throughput for 5M database while not enough main memory for entry cache
When all the performance results above are generated in an ideal controlled environment, we also have done some tests under condition which has not enough main memory to hold entire data entries in entry cache. We used the 5M entries as our test database, and test setup as described at Appendix C. We set dbcache to 5.5 GB and entry cache to
7.5GB, throughputs from DirMark client run is 7763 operations per second. This is equivalent to that the entry cache is holding 40% of 5M entries. We observed that the main memory usage for
Page 19