E
dit
A
ttach
P
rintable
r7 - 2015-07-02 - 03:41:30 -
LuLu
You are here:
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RTCSystemZPerformanceTesting
>
RTCEEDepBuildTests
<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: Dependency Build 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 4.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 focused on a single user executing a team build. The tests are executed against two sets of data: MortgageApplicationx100 and MortgageApplicationx1000 on z/OS, and "Maillistx100" and "Maillistx1000" on IBMi platform. Unless otherwise specified, the following options are commonly used in the tests executing this scenario:<br/> * Leave the publish build maps option cleared %ENDSECTION{"Intro"}% ---++ Scenario for RTCz Detailed Description The following is a detailed description of the individual steps that are executed in the emulation of this scenario to measure performance data. <table class="gray-table"> <tbody> <tr> <th align="center">Test Steps</th> <th align="center">Description</th> </tr> <tr> <td>1. Perform an initial full build of all the programs included in the test data set</br>2. Change one COBOL file and execute the build</br>3. Change one COPY file and execute the build</br>4. Change all COPY books and rebuild</br> 5. Change all COBOL files and rebuild</td> <td>After a first complete build of all the programs, different changes are performed and a rebuild requested. These requests will rebuild the changed programs and impacted ones. <br/> The COBOL file changed in these tests is "MortgageApplication-JKECMORT\zOSsrc\COBOL\JKECMORT.cbl" <br/> The COPY file changed in these tests is "MortgageApplication-Common\zOSsrc\COPYBOOK\JKEMTCOM.cpy". Modifying this copy will impact four COBOL files: "JKEMLIST.cbl", "JKECSMRT.cbl", "JKECMORT.cbl" and "JKECMAIN.cbl". <br/> Finally, all the copybooks are modified and a build requested making all impacted programs to be built.</td> </tr> </tbody> </table> *Note regarding modified files during tests:* when a replicated data set is used (e.g. Mortgagex100), every replication of the cobol and copybooks files referred here are modified. ---++ Scenario for RTCi Detailed Description The following is a detailed description of the individual steps that are executed in the emulation of this scenario to measure performance data. <table class="gray-table"> <tbody> <tr> <th align="center">Test Steps</th> <th align="center">Description</th> </tr> <tr> <td>1. Perform an initial full build of all the programs included in the test data set</br>2. Change one RPG file and execute the build</br> 3. Change all RPG files and rebuild</td> <td>After a first complete build of all the programs, different changes are performed and an incremental build is requested. These requests will rebuild the changed programs and impacted ones. </td> </tr> </tbody> </table> *Note regarding modified files during tests:* when a replicated data set is used (e.g. Mortgagex100), every replication of the cobol and copybooks files referred here are modified. ---++ 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="SingleTierZ"}% %INCLUDE{"RTCEETestingTopologies" section="SingleTierI"}% ---++ Test Reports Please refer to the below links for the reports related to this scenario. 1.1. [[RationalTeamConcertForZOSPerformanceComparisonBetweenReleases][Rational Team Concert For ZOS Performance Comparison Between Releases]]</br> 1.2. [[RationalTeamConcertForIBMiPerformanceComparisonBetweenReleases][Rational Team Concert For IBMi Performance Comparison Between Releases]] This report provide a release by release comparison of the initial full dependency build performance. 2.1. [[ RTCEEIncrementalBuildComparisonBetweenReleases][Rational Team Concert For z/OS Incremental Build Performance Comparison Between Releases ]]</br> 2.2. [[ RTCEEIncrementalBuildComparisonBetweenReleasesForIBMi][Rational Team Concert For IBMi Incremental Build Performance Comparison Between Releases ]] This report provide a release by release comparison of the incremental dependency build performance. The builds are requested after different changes are performed. ---+++++!! 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
: r7
<
r6
<
r5
<
r4
<
r3
|
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
.