IBM Support

IBM DOORS Next 7.x performance considerations



IBM DOORS Next 7.x changed the underlying data store from Jena to a relational database.  
As a result, underlying queries might run differently in 7.x. 

Some customers encountered issues that impact application performance. 
While performance can depend on specific customer data characteristics and use cases, the information in the table provides insight into some of those types of queries. 


Customers that use DOORS Next 7.x can encounter performance issues with the use cases listed in the table.
The use cases in the table have one of two main categories:
1) The underlying database chooses suboptimal execution plans upon running these use cases. 
 The issues are observed with Oracle or Db2 and impact the database server by causing excessive database calls, which consume significantly more CPU on the database server.  When multiple users are running on the server, these slow queries can queue up and result in sudden increases in CPU (sometimes up to 100% of available CPU).
If you colocate your Engineering Lifecycle Management (ELM) applications on one database server, then these issues impact all applications' performance.
IMPORTANT NOTE: While IBM Engineering Requirements Management DOORS Next 7.0.x can scale to higher levels of data and concurrent users than 6.0.x, the techniques that improve query performance with Db2, and Oracle are not sufficient with Microsoft SQL Server. Our analysis of this issue is on-going. 
We recommend that clients who are using IBM DOORS Next Generation 6.0.x with Microsoft SQL Server do not upgrade to ELM 7.0.x currently
Microsoft SQL Server issues are not listed in this technote.  For more information, see Performance considerations: Microsoft® SQL Server® and IBM® DOORS® Next 7.0.x (Engineering Lifecycle Management)
2) The IBM DOORS Next application (the underlying Java virtual machine) exhausts the allocated maximum heap space.
The use cases listed in the table contain two issues that can cause heap exhaustion from single-user actions (Audit History and Link by attribute).
It is also possible that when the database queries start to overload the database server, the DOORS Next server slows down or becomes unresponsive, eventually requiring a restart.
As always, with any performance issue, run update statistics regularly, as out-of-date statistics can be the cause of reported performance issues.  Db2 users can run "reorgchk" weekly as we advise against using AUTO_STMT_STATS.
Known Use Cases (Bold indicates that the interim fix is available)
User Action
Impact to this user
7.0 interim fix
7.0.1 interim fix
7.0.2 interim fix
Rich hover from other ELM applications User does not see impact. Heavy DB server CPU  Defect 138958 (Oracle®) iFix009 iFix007 iFix002
Long loading times for filtered views (traceability) Filtered views take a long time to load or never load. Defect 138958 (Oracle®) iFix009 iFix007 iFix002
DN Baseline views fail to open
Loading views with many traceability link columns encounters timeout before loading is complete.
Long running queries on db server.
Defect 139809 (Db2) Upgrade to 7.0.2 iFix008 iFix004
Change set delivery
Change set delivery does not complete
Heavy CPU on Db server (Oracle®)
Defect 525879 (Oracle®)  iFix009 iFix007 iFix002
Opening modules from a baseline Opening modules from a baseline is slow Defect 143072 (Db2) n/a n/a  TBC
Compare Baseline

Compare a stream to another stream or baseline is slow. Deliver a stream to another stream is slow, or times out.

Defect 526065 (All) TBA TBA iFix008
Create, delete, or update links in an opt-out project area with several users simultaneously
Standard operations become slower to the user when Links Explorer is open
Long running queries on db server.
Defect 529639(Db2) TBA TBA iFix008
Open Audit History
Audit history fails to load. 
Application JVM runs out of heap space
iFix009 iFix007 iFix002
Link by attribute
Operation times out for the user
Application JVM runs out of heap space
iFix008 iFix007  iFix002
All fixes in the table with a designated interim fix are also available in the most recently released interim fix for that stream. 
You can keep track of defects and interim fixes by referencing the ELM Maintenance Schedule on, and subscribing to individual defects.

The list in the table is not exhaustive.  We have created a section within the Performance report for DOORS Next 7.0.2 iFix008 of additional, less severe, defects that relate to performance.
IBM recommends that you apply the most recently released interim fix before you upgrade and continue to apply the most recently released interim fixes to ensure that you do not encounter known, fixed issues.  The list in the table contains issues that are not yet in an interim fix for awareness and to allow planning for production upgrades.
If you feel you are running into any of these issues, or any additional use cases not listed, open a case with IBM Customer Support. 
The use cases in the table might not be encountered in all clients' systems. 
DOORS Next performance for common use cases can vary greatly depending on the data's characteristics. These key characteristics include the number, size, and type of artifacts in the system and the relationships between them.

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUVLZ","label":"IBM Engineering Requirements Management DOORS Next"},"ARM Category":[{"code":"a8m50000000Cj1WAAS","label":"DOORS Next Generation->Performance"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.0;7.0.1;7.0.2"}]

Document Information

Modified date:
13 January 2022