3.4 Scenario # 4 - Write Intensive Operations with Custom Policies

This write intensive operation is a combination of read/write operations with majority of LDAP modify 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

    • Map Schema Policy

    • Replace String Policy

    • Search Request Policy

  • Number of Servers

    • eDirectory: 2

    • LDAP Proxy: 1

  • Operations Performed:

    Operations

    Operation Distribution by Users

    Policy Used

    Operation Details

    Add Users

    5%

    Replace String Policy and Map Schema Policy

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

    Delete Users

    5%

    Replace String Policy

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

    Modify Users

    20%

    Replace String Policy and Map Schema Policy

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

    Search Users

    70%

    Replace String Policy, Map Schema Policy and Search Request Policy

    This performs a search operation for cn.

  • Hardware Used:

    Server for eDirectory

    Server for LDAP Proxy

    Client (JMeter)

    Make

    Dell

    Dell

    Dell

    Model

    PowerEdge R710

    PowerEdge R710

    PowerEdge R710

    Processor

    Intel Xeon® Platinum 8175M processors

    Intel Xeon® Platinum 8175M processors

    Intel Xeon® Platinum 8175M processors

    Operating System

    Linux – RHEL 8.0

    Linux – RHEL 8.0

    Linux – RHEL 8.0

    RAM (in GB)

    64

    16/32/64

    16 GB

    CPU

    4x4

    4x1/4x2/4x4

    4x2

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

Figure 3-4 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 the following concurrent operations:

RAM of LDAP Proxy Server

No. of LDAP Proxy CPU

No. of Optimal Concurrent Operations

16GB

4

0 - 500

32 GB

4x2

500 - 1000

64 GB

4x4

1000 - 1500

As the average response time increases with load, we recommend you to choose a better hardware for concurrent operations beyond every 500.