Off

17127.78

18463.38

Table 5: Performance in relation to nsslapd-cachesize/nsslapd-cachememsize for various database sizes

Number of Entries	Searches per second with	Searches per second with
in the Database	cachememsize 100% or max,	cachememsize default,
	cachesize -1,	cachesize 1,
	dbcachesize 100% or max	dbcachesize 100% or max
100	19597.22	12049.68
10,000	19169.68	11314.75
100,000	18983.23	11399.68
250,000	18545.38	11056.25
500,000	18487.29	11048.27
1,000,000	18398.92	10817.41

From Table 5, you can see from the second column that if all the entries are cached in the entry cache (cachesize of -1, unlimited entries), and if all the pages are cached in the dbcache, then the search throughput changes minimally, no matter how big the database is. So, the number of database entries does not affect performance as long as all entries are cached. However, as shown from the third column, if only a very small percentage of entries can be held in cache (cachesize of 1), the search throughput for different sizes of databases also varies minimally. So, if dbcachesize is big enough to hold all the pages, then the average exact search throughput for any size of database with HPDS 8.1 will be between around 18398 to 19597 operations/second, depending on the number of entries present in the database (the size of the entry cache). If the cache size is restricted to minimize the number of entries in cache, the average search throughput drops considerably, ranging from around 10817 to 12049 operations/second.

Data collection 5: (Access log on compared to Access log off)

This set of data is collected to show how logging can affect the performance.

•Server: Montvale-based test configuration 8 CPUs @1.6GHz each

•Number of entries: 500K

•Number of client threads: 128

•HPDS parameter settings: nsslapd-dbcachesize and nsslapd-cachememsize are big enough to cache all the entries, and nsslapd-threadnumber is set to 6.

Table 6 shows that by turning the access log off, the exact search throughput can increase about 4% in a Montvale-based test bed.

Table 6: Performance in relation to nsslapd-accesslog setting: (on or off) Access log on or off Searches per second

Data collection 6: (SSL connection enabled compared to SSL connection disabled)

This set of data is collected to show the performance impact if SSL connection is enabled or disabled.

•Server: Montvale-based test configuration 8 CPUs @1.6GHz each

•Number of entries: 500K

•Number of client threads: 128

•HPDS parameter settings: assume nsslapd-dbcachesize and nsslapd-cachememsize are big enough to cache all the entries. nsslapd-threadnumber is set to 6.

•Special setting in client: “Bind for every operation” option is selected.

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.