E
dit
A
ttach
P
rintable
r7 - 2020-05-06 - 13:54:54 -
TimFeeney
You are here:
TWiki
>
Deployment Web
>
DeploymentMonitoring
>
CLMExpensiveScenarios
>
ScenariosToBeInvestigated
e<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! CLM Scenarios to Investigate as Potentially Expensive%RED%(DRAFT)%ENDCOLOR% <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> %DKGRAY% Authors: Main.TimFeeney <br> Build basis: The Rational solution for Collaborative Lifecycle Management (CLM) and the Rational solution for systems and software engineering (SSE) v6.0.1. %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> This page captures CLM scenarios that may potentially be expensive but need further investigation to characterize and confirm. See the parent topic containing the [[https://jazz.net/wiki/bin/edit/Deployment/CLMExpensiveScenarios][known]] list. %RED%Note: The information herein is a work in progress and is continually being reviewed/refined%ENDCOLOR% | %BLUE% *Table 1: Summary of CLM Scenarios to Investigate* %ENDCOLOR% ||||| | *Product* | *Scenario* | *Scenario ID* | *Best Practice* | *Investigate* | | [[#Rational_DOORS_Next_Generation][Rational DOORS Next Generation (DRAFT)]] | [[#Comparing_local_configurations_w][Comparing local configurations with large number of artifacts]] | DNG_Compare_Configuration | link | [[https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=106102][106102]] | | ||||| | [[#Rational_Team_Concert][Rational Team Concert (DRAFT)]] | [[#Concurrently_loading_a_large_num][Concurrently loading a large number of large configurations]] | RTC_Load_Workspace | link | [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389280][389280]] | | ^ | [[#Import_of_large_CSV_files][Import of large CSV files]] | RTC_CSV_Import | link | [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389357][389357]] | | ^ | [[#Export_of_large_number_of_work_i][Export of large number of work items to CSV file]] | RTC_Workitem_Export | link | [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389359][389359]] | | ^ | [[#Large_bulk_edits_of_work_items][Large bulk edits of work items]] | RTC_WI_Bulk_Edit | link | [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389361][389361]] | | ||||| | [[#Rational_Quality_Manager][Rational Quality Manager (DRAFT)]] | [[#Comparing_local_configuratio_AN1][Comparing local configurations with large number of artifacts]] | RQM_Compare_Configuration | link | [[https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=151178][151178]] | | ||||| | [[Jazz_Reporting_Services_all_repo][Jazz Reporting Services (all reporting technologies) (DRAFT)]] | | | | | | ||||| | [[#Global_Configuration][Global Configuration (DRAFT)]] | | | | | ---++ Rational DOORS Next Generation ---+++ Comparing local configurations with large number of artifacts %RED% This scenario needs further analysis to confirm it can be expensive and to characterize further. See [[https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=106102][work item 106102]] %ENDCOLOR% ---++ 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 [[https://jazz.net/wiki/bin/view/Deployment/EnvelopesRangesAndLimits#RTC][RTC Limits]]). %RED% This scenario needs further analysis to confirm it can be expensive and to characterize further. See [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389280][work item 389280]]. %ENDCOLOR% ---+++ 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. %RED% Further investigation to better characterize a 'large' CSV file import and the load generated when importing one is tracked by [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389357][work item 389357]]. %ENDCOLOR% ---++++!! 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. %RED% Further investigation to better characterize a 'large' number of work items and the load generated when exporting them is tracked by [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389359][work item 389359]]. %ENDCOLOR% ---+++ 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. %RED% This scenario needs further analysis to confirm it can be expensive and to characterize further. See [[https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=389361][work item 389361]]. %ENDCOLOR% ---+++ Slow running scenarios ---++++!! Synchronizing attributes after a large amount of change in attributes for a work item There are two ways for [[http://www-01.ibm.com/support/docview.wss?uid=swg21372230][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 %RED% This scenario needs further analysis to confirm it can be expensive and to characterize further. See [[https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=151178][work item 151178]]. %ENDCOLOR% ---++ Jazz Reporting Services (all reporting technologies) ---++ Global Configuration ------- ---+++++!! Related topics: ---+++++!! External links: </div>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r7
<
r6
<
r5
<
r4
<
r3
|
M
ore topic actions
Deployment.ScenariosToBeInvestigated moved from Deployment.OperationsToBeInvestigated on 2016-05-11 - 08:49 by
TimFeeney
-
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.