E
dit
A
ttach
P
rintable
r5 - 2014-11-21 - 17:01:15 -
JorgeAlbertoDiaz
You are here:
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RTCSystemZPerformanceTesting
>
RTCEEWorkloadTests
<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%"> ---+!! RTCEE Performance Testing: EE Workload Scenario<img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> %DKGRAY% Authors: [[Main.JorgeAlbertoDiaz][Jorge Diaz]] <br> Build basis: RTC 5.x %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> %STARTSECTION{"Intro"}% This scenario tests the performance of the Enterprise Dependency Based Build feature under a high volume workload, simulating concurrent build operations that developers would execute in a real case scenario.<br/> The tests scenario themselves are based on observations of the usage performed by our customers and our recommended practices to them. %ENDSECTION{"Intro"}% ---++ Scenario Detailed Description The scenario presents the following situation: enterprise deployment of Rational Team Concert. Several development teams work in building different applications (COBOL/CICS applications). Each team has a development integration stream for consolidating their work and building changes in a regular basis. The idea is to try to mimic a real case scenario usually found in the field where we see a Project Area representing a "program" (group of applications), and different teams which can map to business units develop their own application. Different roles have been considered in the tests automation to reflect different sort of changes, and also to consider the load that either a developer or a different kind of role would impose by modifying work items. Note that this concept of business units related development teams can be mapped to other organizations that divide them in a per-Project Area basis (instead of teams); this is still valid where the actual focus of the test is in the load that the level of changes and builds concurrency imposes, and how the server reacts; where logical teams-projects variances do not represent a matter of concern. ---+++ RTC Parametrization This section describe any parameters different from the default ones, which are relevant for the execution of the tests. ---++++ RTC Server Configuration Options The following configuration properties values have been set at server level: * Set advance property: 'Consider only outgoing change sets in personal builds = true' * Customization of the _Asynchronous Task Pool Size_ parameter for the amount of concurrent builds that will be executed. * Source Code Data Collection: customize the Max Number of Files in _Source Code Data Resource_ parameter to a maximum value of 100: <img src="%ATTACHURLPATH%/scdConfig.png"/> ---++++ RTC Test Assets Configuration Different RTC elements are created to execute the activities and load expected. The following is a collection of the relevant parameters that have been set in these elements: * Personal builds requested will have the Minimum Load option set * Several streams are used in these tests. These streams have *not* been generated using the Duplicate stream feature. Duplicating a stream causes the Source Code Data to be reused, while for the tests information gathering it is preferred that every stream has different set of SCD. * System Definitions: 4.0.3 Link-edit feature will not be used. * Build Engines configuration: Build engines should be configured in such a manner that it is assured that a team build request doesn't impact personal builds concurrency. To accomplish that, the following property is added to the build engines that will be serving personal builds: requestFilter with value personalBuild=true: <img src="%ATTACHURLPATH%/buildFilter.png"/> ---+++ Test Assets Preparation In addition to configuring the RTC elements that will be used in the test to support the behavior; the test framework assets have to be configured as well in order to make them reproduce the activities and load expected. There are two important configuration areas to consider: (a) the emulated/virtual users; and (b) how the data was initialized in RTC. ---++++ Virtual Users Characterization To emulate the load and the main tasks expected during real solution usage, the following roles and operations have been identified. <br/> These are used in the testing framework to emulate real users operations at the load and rates finer specified later in this topic: <table class="gray-table"> <tr> <th><strong>Activities\Role</strong></th> <th><strong>Developer A</strong></th> <th><strong>Developer B</strong></th> <th><strong>Contributor</strong></th> </tr> <tr> <td></td> <td>Change a COBOL program<br/> Check-in the changes<br/> Request Personal Build to verify changes<br/> Accept incoming changes<br/> Deliver the change sets<br/> </td> <td>Change a copybook source<br/> Check-in the changes<br/> Request Personal Build to verify changes<br/> Accept incoming changes<br/> Deliver the change sets<br/> </td> <td>Log in to repository<br/> Create and save a work item<br/> Execute a query (25% of times) -- just execute query every 4 iterations<br/> Logout<br/> </td> </tr> </table> <br/> ---++++ Scenario execution preparation Following are the main steps for preparing the environment for the test scenario run. The steps are beyond creating and configuring the assets already described: 1. Assign/verify Build System definitions with sample resources 1. Perform a full build of the applications 1. Load the virtual developers workspaces in preparation for the test run. <br/> ---++ Test Topologies The following topologies are being used for the execution of this scenario in order to test the performance and gather relevant data. %INCLUDE{"RTCEETestingTopologies" section="DualTierZ"}% ---++ Test Data From the existing scalability test data based on [[https://jazz.net/wiki/pub/Main/ZOSBuildSamplesV4/MortgageApplication.zip][Mortage Application]] sample, the following will be used: %INCLUDE{"RTCEEPerfTestsData" section="Mortx500"}% ---++ Scenario Variances Based on the previous detailed configuration, two variances of the scenario are tested: ---+++ Test Scenario 1 The following SCM structure is used: * 50 components distributed among 25 streams * Each stream will hold 2 of the components with the test data sample distribution: one component will hold the common project of called MortgageApplication-Common, where the other component contains the rest of projects The following screenshot shows a sample configuration of one of the streams: <img src="%ATTACHURLPATH%/streamConf1.png"/> <img src="%ATTACHURLPATH%/streamConf2.png"/> * 30 build engines targeting the same build agent. This will allow the concurrency described later and the team builds execution. * 25 build engines will be configured to just accept personal builds * One build definition for each stream representing the build of the test data application * Each stream will have a team build with associated: * A build workspace * A defined HLQ and load directory for every team / build definition * Each virtual user will need to have defined: * A personal repository workspace flowing to the assigned stream * A personal HLQ and load directory on the build machine * Personal workspace, HLQ and load directory will be used in the automated build requests processing The scenario is meant to be performed during a long run of *8 hours*, trying to emulate a system load during a work day, with the following details: * The emulation will try to reproduce a scenario during a work day and variations of work load to different applications and streams. Similar to what would be normal lifecycle of development enterprise work, where some applications are more active than others. * From the 25 defined streams, 10 would be identified as more active ones, with users and load described in next subpoints. * Simulation of *28 concurrent developers* work. * Following distribution of emulated developers and streams: 2 streams will have 7 concurrent developers with the following roles and files to be modified in each iteration: <table class="gray-table" style="width: 70%"> <tr> <th><strong>Role</strong></th> <th><strong>#users</strong></th> <th><strong>Files to modify<br/>(1 line per developer)</strong></th> </tr> <tr> <td>Developer role A</td> <td>6 (per stream)</td> <td>AAACMORT.cbl / AABCMORT.cbl / AACCMORT.cbl<br/> AADCMORT.cbl / AAECMORT.cbl / AAFCMORT.cbl<br/> AAGCMORT.cbl / AAHCMORT.cbl / AAICMORT.cbl<br/> AAJCMORT.cbl / AAKCMORT.cbl / AALCMORT.cbl<br/> AAMCMORT.cbl / AANCMORT.cbl / AAOCMORT.cbl<br/> AAPCMORT.cbl / AAQCMORT.cbl / AARCMORT.cbl </td> </tr> </tr> <tr> <td>Developer role B</td> <td>1 (per stream)</td> <td>AAAMLIS.bms / AAAMTCOM.cpy / AABMLIS.bms / AABMTCOM.cpy </td> </tr> </table> 3 streams will have 3 concurrent developers with the following roles and files to be modified in each iteration: <table class="gray-table" style="width: 70%"> <tr> <th><strong>Role</strong></th> <th><strong>#users</strong></th> <th><strong>Files to modify<br/>(1 line per developer)</strong></th> </tr> <tr> <td>Developer role A</td> <td>2 (per stream)</td> <td>AAACMORT.cbl / AABCMORT.cbl / AACCMORT.cbl<br/> AADCMORT.cbl / AAECMORT.cbl / AAFCMORT.cbl </td> </tr> </tr> <tr> <td>Developer role B</td> <td>1 (per stream)</td> <td>AAAMLIS.bms / AAAMTCOM.cpy / AABMLIS.bms / AABMTCOM.cpy</td> </tr> </table> 5 streams will have 1 developer assigned: 1:1 relationship between developers and streams: <table class="gray-table" style="width: 70%"> <tr> <th><strong>Role</strong></th> <th><strong>#users</strong></th> <th><strong>Files to modify<br/>(1 line per developer)</strong></th> </tr> <tr> <td>Developer role A</td> <td>1 (per stream)</td> <td>AAACMORT.cbl / AABCMORT.cbl / AACCMORT.cbl</td> </tr> </table> <br/> Additionally, one *team build will be requested at every hour* for each of the streams: not scheduled to start at same hour every time but with a difference of 10 minutes., so not all the team builds are executed at same hour time. ---++++ Test Reports Information about the results of this test can be found in [[https://jazz.net/wiki/bin/view/Deployment/RTCEEWorkloadTestScenario1Report][this topic]] . ---+++ Test Scenario 2 The following SCM structure is used: * 150 components distributed among 25 streams: * Each stream with 6 components with the test data distribution, using a different set of qualified file names The following screenshot shows a sample configuration of one of the streams: <img src="%ATTACHURLPATH%/streamConf1.png"/> * 60 build engines targeting the same build agent. This will allow the concurrency described later and the team build. * 50 build engines will be configured to just accept personal builds * Three build definitions for each stream for building each set of the testing data * Each stream will have a team build with associated: * Build workspace * Defined HLQ and load directory for every team / build definition * Each virtual user will need to have defined: * A personal repository workspace flowing to the assigned stream * A personal HLQ and load directory on the build machine * Personal workspace, HLQ and load directory will be used in the automated build requests processing The emulation will try to reproduce a scenario during a work day and variations of work load to different applications and streams. Similar to what would be normal lifecycle of development enterprise work, where some applications are more active than others: as Scenario 1 but emulating a system with heavier load: * From the 25 defined streams, 11 would be identified as more active ones, with users and load described in next subpoints. * Simulation of 75 concurrent developers. * Following distribution of emulated developers and streams: 3 streams will have 7 concurrent developers with the following roles and files to be modified in each iteration: <table class="gray-table" style="width: 70%"> <tr> <th><strong>Role</strong></th> <th><strong>#users</strong></th> <th><strong>Files to modify<br/>(1 line per developer)</strong></th> </tr> <tr> <td>Developer role A</td> <td>9 (per stream)</td> <td>AAACMORT.cbl / AABCMORT.cbl / AACCMORT.cbl<br/> AADCMORT.cbl / AAECMORT.cbl / AAFCMORT.cbl<br/> AAGCMORT.cbl / AAHCMORT.cbl / AAICMORT.cbl<br/> AAJCMORT.cbl / AAKCMORT.cbl / AALCMORT.cbl<br/> AAMCMORT.cbl / AANCMORT.cbl / AAOCMORT.cbl<br/> AAPCMORT.cbl / AAQCMORT.cbl / AARCMORT.cbl<br/> AAQCMORT.cbl / AARCMORT.cbl / AASCMORT.cbl<br/> AATCMORT.cbl / AAUCMORT.cbl / AAWCMORT.cbl<br/> AAXCMORT.cbl / AAYCMORT.cbl / AAZCMORT.cbl </td> </tr> </tr> <tr> <td>Developer role B</td> <td>3 (per stream)</td> <td>AAAMLIS.bms / AAAMTCOM.cpy / AABMLIS.bms / AABMTCOM.cpy<br/> AACMLIS.bms / AACMTCOM.cpy / AADMLIS.bms / AADMTCOM.cpy<br/> AAEMLIS.bms / AAEMTCOM.cpy / AAFMLIS.bms / AAFMTCOM.cpy</td> </tr> </table> 5 streams will have 6 concurrent developers with the following roles and files to be modified in each iteration: <table class="gray-table" style="width: 70%"> <tr> <th><strong>Role</strong></th> <th><strong>#users</strong></th> <th><strong>Files to modify<br/>(1 line per developer)</strong></th> </tr> <tr> <td>Developer role A</td> <td>5 (per stream)</td> <td>AAACMORT.cbl / AABCMORT.cbl / AACCMORT.cbl<br/> AADCMORT.cbl / AAECMORT.cbl / AAFCMORT.cbl<br/> AAGCMORT.cbl / AAHCMORT.cbl / AAICMORT.cbl<br/> AAJCMORT.cbl / AAKCMORT.cbl / AALCMORT.cbl<br/> AAMCMORT.cbl / AANCMORT.cbl / AAOCMORT.cbl </td> </tr> </tr> <tr> <td>Developer role B</td> <td>1 (per stream)</td> <td>AAAMLIS.bms / AAAMTCOM.cpy / AABMLIS.bms / AABMTCOM.cpy<br/> AACMLIS.bms / AACMTCOM.cpy / AADMLIS.bms / AADMTCOM.cpy</td> </tr> </table> 3 streams will have 3 developers assigned: 1:1 relationship between developers and streams: <table class="gray-table" style="width: 70%"> <tr> <th><strong>Role</strong></th> <th><strong>#users</strong></th> <th><strong>Files to modify<br/>(1 line per developer)</strong></th> </tr> <tr> <td>Developer role A</td> <td>3 (per stream)</td> <td>AAACMORT.cbl / AABCMORT.cbl / AACCMORT.cbl</td> </tr> </table> <br/> Repeating the role steps at cycles of 30 minutes. Additionally, one team build will be requested at every hour for each of the streams: not scheduled to start at same hour every time but with a difference of 10 minutes., so not all the team builds are executed at same hour time. ---+++++!! Related topics: ---+++++!! External links: * [[https://www.ibm.com][IBM]] ---+++++!! Additional contributors: <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
M
ore topic actions
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
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.