2.1 Scenario # 1 - Read Intensive Operations

This read intensive operation is a combination of read/write operations with majority of LDAP search user operation. We have considered the following hardware and configuration parameters for this test:

  • Product Version:

    • eDiretory 9.1 SP3

    • LDAP Proxy 1.5 SP3

  • Policy Configured:

    • Connection Route Policy

  • Number of Servers

    • eDirectory: 2

    • LDAP Proxy: 1

  • Operations Performed:

    Operations

    Operation Distribution by Users

    Operation Details

    Add Users

    5%

    This adds users with DN, such as cn=userX. Each object has only sn attribute defined.

    Delete Users

    5%

    This deletes users with DN, such as cn=userX.

    Modify Users

    20%

    This modifies user object such as cn=userX with the following attribute modified: replace => [ title => "EngineerX" ]

    Search Users

    70%

    This performs a search operation for cn.

  • Hardware Used:

    Server (LDAP and eDirectory)

    Client (JMeter)

    Make

    Dell

    Dell

    Model

    PowerEdge R710

    PowerEdge R710

    Processor

    Intel Xeon CPU X5670 @2.93GHz

    Intel Xeon CPU X5670 @2.93GHz

    Operating System

    Linux – SLE12SP2

    Linux – SLE12SP2

    RAM

    16 GB

    16 GB

    CPU

    4x2

    4x2

The following graphical representation shows how average response time change while performing the above-mentioned operations concurrently:

Figure 2-1 Change in average response time based on number of operations performed concurrently

Recommendation

As per this read intensive test, the specified hardware can be used for optimal performance if 0 - 300 concurrent operations are performed. This hardware can also support up to 500 concurrent operations. As the average response time increases with load, we recommend you to choose a better hardware for concurrent operations beyond 500.