What kind of footprint does the Virtual Directory Server have?
At run-time, the main code for the VDS is about 4 MB on disk. With the different Java libraries and utilities a rough estimate of the working set before any data allocation is around 12-15 MB. This number does not include the footprint of the JVM environment itself. In terms of memory occupation the VDS cache -configurable- represents the major part. The server is fully multi-threaded and scales fully linearly up to 4 to 6 processors. After that, scalability continues but not fully linearly. The VDS doesn?t have a back-end per se when the persistent cache function is not enabled. If the persistent cache is turned on then VDS provides its own full LDAP back-end (Tests have been done with cache supporting more than 100 millions entries per back-end). Optionally, the back-end used for persistence and write through cache could be any high performance LDAP V3 server.
At run-time, the main code for the VDS is about 4 MB on disk. With the different Java libraries and utilities a rough estimate of the working set before any data allocation is around 12-15 MB. This number does not include the footprint of the JVM environment itself. In terms of memory occupation the VDS cache -configurable- represents the major part. The server is fully multi-threaded and scales fully linearly up to 4 to 6 processors. After that, scalability continues but not fully linearly. The VDS doesn?t have a back-end per se when the persistent cache function is not enabled. If the persistent cache is turned on then VDS provides its own full LDAP back-end (Tests have been done with cache supporting more than 100 millions entries per back-end). Optionally, the back-end used for persistence and write through cache could be any high performance LDAP V3 server.
