Introduction

In the ELM 7.3.0 release, significant performance improvements were made to TRS validation across multiple ELM applications — DOORS Next , Engineering Test Management (ETM), and Engineering Workflow Management (EWM). These improvements reduce the time required to complete TRS validation, thereby reducing the operational overhead for customers who run TRS validation as part of their maintenance or troubleshooting workflows.

This article presents the performance test results for TRS validation improvements in ELM 7.3.0 for the following applications:

• DOORS Next — covered in this article
• Engineering Test Management (ETM) — covered in this article
• Engineering Workflow Management (EWM) — section reserved for team member contribution

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 TRS validation testing in ELM 7.3.0:

• Doors Next: TRS validation time for a DOORS Next repository of approximately 1.5 million records and 1,126 baselines was reduced from 8 hours 9 minutes 44 seconds to 53 minutes 23 seconds (tested without the "clear cache" option). This represents approximately a 9x improvement in TRS validation speed.

• ETM: The Skip Step Results enhancement reduced TRS resource volume by nearly 50% (from approximately 6.7 million to 3.45 million resources ) and significantly improved the performance of ETM TRS rebase, ETM TRS validation, LQE validation, and LQE re-indexing operations. Performance improvements ranged from 38% to 45%, demonstrating substantial scalability benefits for large ETM deployments.

• EWM: Needs to Add once ready

Upgrading to ELM 7.3.0 will result in meaningfully shorter TRS validation windows, particularly for large deployments that run validation after upgrades, database restores, or as part of routine maintenance.

DOORS Next TRS Validation Performance

Test Methodology

This section describes the data used for testing, the test environment, and the approach taken to measure TRS validation performance.

Data Shape

TRS validation performance testing for DOORS Next was performed against a repository with the following characteristics:

Testing Approach

TRS validation was triggered manually against the DOORS Next application. The test compared the time taken to complete a full TRS validation run before and after the 7.3.0 performance improvement, using the same repository and the same server environment.

Key testing parameters:

• Database: Oracle
• TRS validation mode: Standard validation (without the "clear cache" option)
• Comparison: Pre-improvement baseline (representing behavior prior to the 7.3.0 fix) vs. post-improvement (7.3.0)

Test Environment Details

Performance Test Results

Summary of Results

• TRS validation time was reduced from approximately 8 hours 10 minutes to approximately 53 minutes — a reduction of over 7 hours.
• This is approximately a 9x improvement in validation speed for a repository of ~1.5 million records and 1,126 baselines.
• The improvement is available by default in ELM 7.3.0. No additional configuration or enabling of advanced properties is required.
• Testing was performed with Oracle as the database backend, without the clear cache option.

Detailed Results

The table below summarizes the TRS validation duration before and after the 7.3.0 improvement.

ETM TRS Validation Performance

Test Methodology

Testing in the PVT environment compared the same operations before and after enabling ETM Skip Step Results. Both runs used the same ETM repository, test scenarios and execution sequence.

The following operations were measured:

• ETM TRS rebase
• LQE validation
• LQE re-indexing
• ETM TRS validation

TRS console values (bases, base pages, change events) and repository version counts were also recorded before and after, to check for changes in TRS volume or repository content.

Data Shape

The same ETM repository was used for both runs. The repository contained about 243 million versions, including about 5.2 million step-result version states and about 7.6 million version states for everything else. The implementation changed none of these counts.

Testing Approach

The same test sequence was followed for both Skip Step Results Disabled and Enabled runs:

• Capture the initial TRS Console metrics and repository statistics.
• Perform an ETM TRS rebase and record the completion time.
• Perform LQE validation and record the base-processing and removal-processing durations.
• Perform LQE re-indexing and record the completion time.
• Perform ETM TRS validation and record the completion time.
• Capture the final TRS Console metrics and repository statistics for comparison.

The baseline run was performed with the Skip Step Result from TRS Processing property set to its default value of false. For the comparison run, the property was set to true before performing the ETM TRS rebase.

Test Environment Details

Performance Test Results

Summary of Results

With Skip Step Results enabled, testing showed these improvements:

• ETM TRS rebase: Reduced from approximately 1 day 15 hours to approximately 24 hours, a reduction of about 15 hours (38.8% faster).
• LQE validation: Base processing was reduced from approximately 4 hours 8 minutes to approximately 2 hours 29 minutes, a reduction of about 1 hour 39 minutes (39% faster).
• LQE re-indexing: Reduced from approximately 4 days 20 hours to approximately 2 days 16 hours, a reduction of about 2 days 4 hours (44.8% faster).
• ETM TRS validation: Reduced from approximately 2 days 3 hours to approximately 1 day 7 hours, a reduction of about 19.5 hours (38.4% faster).

Detailed Results

LQE validation: After an ETM rebase, the first LQE operation also runs a one-time removal phase that clears step results already indexed in LQE. It is not repeated by later operations. The increase in total validation time comes from this phase, not from slower base processing.

EWM TRS Validation Performance

This section will be populated by the EWM team member. Performance test results, data shape details, environment information, and key findings for EWM TRS validation improvements in ELM 7.3.0 will be added here.

Test Methodology

To be added.

Data Shape

To be added.

Testing Approach

To be added.

Test Environment Details

To be added.

Performance Test Results

To be added.

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