CLM Scenarios to Investigate as Potentially Expensive(DRAFT)

Authors: TimFeeney
Build basis: The Rational solution for Collaborative Lifecycle Management (CLM) and the Rational solution for systems and software engineering (SSE) v6.0.1.

This page captures CLM scenarios that may potentially be expensive but need further investigation to characterize and confirm. See the parent topic containing the known list.

Note: The information herein is a work in progress and is continually being reviewed/refined

Table 1: Summary of CLM Scenarios to Investigate
Product	Scenario	Scenario ID	Best Practice	Investigate
Rational DOORS Next Generation (DRAFT)	Comparing local configurations with large number of artifacts	DNG_Compare_Configuration	link	106102
Rational Team Concert (DRAFT)	Concurrently loading a large number of large configurations	RTC_Load_Workspace	link	389280
	Import of large CSV files	RTC_CSV_Import	link	389357
	Export of large number of work items to CSV file	RTC_Workitem_Export	link	389359
	Large bulk edits of work items	RTC_WI_Bulk_Edit	link	389361
Rational Quality Manager (DRAFT)	Comparing local configurations with large number of artifacts	RQM_Compare_Configuration	link	151178
Jazz Reporting Services (all reporting technologies) (DRAFT)
Global Configuration (DRAFT)

Rational DOORS Next Generation

Comparing local configurations with large number of artifacts

This scenario needs further analysis to confirm it can be expensive and to characterize further. See work item 106102

Rational Rhapsody Design Manager

Importing or moving a large model to DM

When you import a large model, or move a large model (in actively-managed mode) to DM, the server could potentially become unresponsive, especially when others are working in that same stream. DM notifies users that an import is occurring.

Scenarios that load a large model

Some scenarios require loading a model in its entirety; if the model is large, it can impact server memory and processing. Such scenarios include:

• Generating code from a model
• Exporting a model (using “Save as”)
• Creating a table layout in Rhapsody with too broad a scope

Use smaller related models to reduce the system demands; this is also a best practice.

OSLC integration to DNG/DOORS

Rhapsody DM can manage OSLC links between model elements and requirements artifacts in related DOORS and DNG projects. When doing so, DM retrieves all available requirements from the projects and all defined links from the DM server. The integration synchronizes to find new requirements/links. If the requirements project is large, the link management can be resource-intensive.

To reduce resource demands, use a filtered view (e.g. collection, module) to narrow the amount of requirements to retrieve.

Rational Team Concert

Concurrently loading a large number of large configurations

This may occur with many continuous builds doing many concurrent loads of large configurations (those approaching the file/folder limit as described in RTC Limits).

This scenario needs further analysis to confirm it can be expensive and to characterize further. See work item 389280.

Import of large CSV files

Similar to an import of a Microsoft Project plan, an import of a large CSV file can keep the server busy and drive memory usage. However, unlike the plan import, CSV file imports occur more frequently and are often part of a round trip update.

Further investigation to better characterize a 'large' CSV file import and the load generated when importing one is tracked by work item 389357.

Best Practices for Import of large CSV files

For more than 1000 work items, it is best to wait for off hours or until the server is lightly loaded.

Export of large number of work items to CSV file

Exporting a large number of work items primarily impacts memory on the server.

Further investigation to better characterize a 'large' number of work items and the load generated when exporting them is tracked by work item 389359.

Large bulk edits of work items

Performance and load driven by this scenario is a function of the number of work items and number of attributes changed as each work item is changed and saved one at a time.

This scenario needs further analysis to confirm it can be expensive and to characterize further. See work item 389361.

Slow running scenarios

Synchronizing attributes after a large amount of change in attributes for a work item

There are two ways for synchronizing work item attributes. First, using the RTC Eclipse client, run a query and select a set of work items then right click the type column and select Synchronize Attributes. This process would only affect the selected work items and response time is not a concern unless the client selected thousands of work items. The second method is to trigger the sync from the process configuration editor by the "check attributes usages in repository" action. This process could take a long time as it sync all work items created with all work item types within the same project area. If there are thousands of work items in the project area with a large number of attributes changes, it can take some time to complete (a warning is presented to the user).

Loading a work item with a large amount of customized attributes

When there are over 100 custom attributes in a work item type, loading of a work item of that type can be slow from the client perspective but isn't known to drive server load.

Rational Quality Manager

Comparing local configurations with large number of artifacts

This scenario needs further analysis to confirm it can be expensive and to characterize further. See work item 151178.

Jazz Reporting Services (all reporting technologies)

Global Configuration

---

Related topics:

External links: