Introduction

In ELM 7.3.0, significant performance improvements were introduced in the discovery of RM–RMM links by leveraging LDX/LQE rather than relying on direct OSLC queries. In ELM 7.2.0, RM directly queries RMM through OSLC to discover these links. As the number of project associations increases, these direct queries can become increasingly time-consuming, negatively impacting module view performance.

To address this limitation, ELM 7.3.0 introduces a development enhancement that enables RM to use LDX/LQE for RM–RMM link discovery wherever possible, thereby reducing reliance on direct RMM queries and improving performance.

This article presents the performance test results for the RM–RMM link discovery enhancement introduced in ELM 7.3.0, comparing the LDX/LQE-based approach with the OSLC-based approach used in ELM 7.2.0. It also presents performance on both DB2 and Oracle databases.

Standard Disclaimer

The information in this document is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites. Any performance data contained in this document was determined in a controlled environment, and therefore, the results that may be obtained in other operating environments may vary significantly. Users of this document should verify the applicable data for their specific environment.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multi-programming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

This testing was done as a way to compare and characterize the differences in performance between different versions of the product. The results shown here should thus be looked at as a comparison of the contrasting performance between different versions, and not as an absolute benchmark of performance.

Key Findings

The following summarizes the key performance findings from RM–RMM link discovery validation testing in ELM 7.3.0:

• Time for opening module view with 30 users of a large component module having 10k artifacts and 60k RM-RMM links was reduced from approximately 187 seconds (in OSLC mode) to approximately 4 seconds (in LDX mode). This represents approximately a 47x improvement with LDX for links discovery speed.
• LDX mode showed better scalability than OSLC. OSLC degraded beyond 30 users, while LDX successfully supported 500 users on both DB2 and Oracle.

RM-RMM Links Discovery Performance

Performance Test Results

Summary of Results

• Time for opening view in module with 30 users was reduced from approximately 187 seconds (in OSLC mode) to approximately 4 seconds (in LDX mode) — a reduction of over 183 seconds.
• This is approximately 47x faster with LDX for a Large Component Module having 10k artifacts and around 60k RM to RMM links.
• The improvement is available with LDX mode in ELM 7.3.0. By default, links discovery mode is OSLC and hence enabling of advanced properties "Use LDX for Linking" is required.
• Testing was performed with both Oracle and DB2 as the database backend.
• LDX mode showed better scalability than OSLC. OSLC degraded beyond 30 users, while LDX successfully supported 500 users on both DB2 and Oracle.

Detailed Results

I. Page Response Comparison of OSLC vs LDX on DB2 for 30 Users

II. Page Response Comparison of OSLC vs LDX on Oracle for 30 Users

III. Page Response Comparison with LDX Mode for DB2 vs Oracle vs Users

LDX mode demonstrated consistent and significantly lower response times compared to OSLC across all user load levels on both DB2 and Oracle databases. As user load increased beyond 30 concurrent users, OSLC mode degraded significantly, while LDX mode maintained stable and low response times, successfully scaling to 500 users on both database backends.

Test Methodology

This section describes the data used for testing, the test environment, and the approach taken to measure RM-RMM Links discovery performance.

Data Shape

RM-RMM Links discovery performance testing was performed for opening module view against DNG Large Component Module with the following characteristics:

Testing Approach

Discovery of RM-RMM Links was done using script for opening module view. The test compared the time taken to load links in view for both OSLC and LDX mode against ELM 7.3.0, using the same data shape and the same server environment.

Key testing parameters:

• Database (one by one): Oracle, DB2
• Link discovery: Testing was performed for opening module views against DNG large component module having 10k artifacts and around 60k RM to RMM links
• Comparison: OSLC Mode (baseline) (representing behavior prior to the 7.3.0 changes) vs. LDX Mode (7.3.0 changes)

Test Environment Details

Abbreviations

• CCM = Change and Configuration Management (Engineering Workflow Management SCM component)
• DN = DOORS Next Generation (Engineering Requirements Management)
• ELM = Engineering Lifecycle Management
• ETM = Engineering Test Management
• EWM = Engineering Workflow Management
• IHS = IBM HTTP Server
• JTS = Jazz Team Server
• LDX = Link Index Provider
• LQE = Lifecycle Query Engine
• QM = Quality Management (ETM application context)
• RM = Requirements Management (DN application context)
• TRS = Tracked Resource Set