E
dit
A
ttach
P
rintable
r14 - 2014-10-22 - 06:49:58 -
LuLu
You are here:
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RationalTeamConcertOnZOSPerformance406
<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%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"> Rational Team Concert for z/OS performance impact of Java JFS API adoption in 4.0.6 %DKGRAY% Authors: [[Main.SuHui][Su Hui]] <br> Last updated: December 6, 2013 <br> Build basis: Rational Team Concert on ZOS 4.0.6 & 4.0.5 %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> ---++ Introduction This report compares the performance of RTC for z/OS of version 4.0.6 to the previous 4.0.5 release. RTC for z/OS v4.0.6 includes an enhancement by adopting the Java JFS API for some of the queries. The test objective is to ensure there is no regression and verify the performance improvement for the new Java JFS API adoption. ---++ Disclaimer %INCLUDE{"PerformanceDatasheetDisclaimer"}% ---++ Findings Based on the test data, performance of the RTC for z/OS has an improvement in Enterprise Extensions dependency build preprocessing speeds from 4.0.5 to 4.0.6: * In the scenario of the incremental build (request build after changing all the copybook files), the *"Collecting buildable files" activity in preprocessing time improved about 25%*, and result in an about 5% improvement in total run time. For other scenarios performance stayed consistent between the two versions. ---++ Topology The tests are executed in a Single Tier Topology infrastructure like the one in the following diagram: <img src="%ATTACHURLPATH%/singleTierRTCEETests.png" alt="singleTierRTCEETests.png" width="80%" height="80%"/> The RTC server was set up based on !WebSphere and DB2 on Linux for System z. The build machine with Rational Build Agent was on zOS. <table class="gray-table"> <tr> <th><strong>Test Environment</strong></th> <th></th> <th></th> </tr> <tr> <td><strong>RTC Server</strong></td> <td>Operating System & Version: Linux for System z (SUSE Linux Enterprise Server 10 (s390x))</br> System Resource : 10 GB Storage, 4 CPs (20000 mips, CPU type : 2097.710, CPU model: E12) </br> CLM: 4.0.6 M2 (CALM-I20131211-0734), 4.0.5 GA (CALM-I20131025-2323), 4 GB heap size </br> DB2: 9.7.0.5 </br> WAS: 8.0.0.3 </br> </td> <tr> <td><strong>Build Forge Agent</strong></td> <td>Operating System & Version: z/OS 01.12.00</br> System Resource: 6 GB Storage, 4 CPs (20000 mips, CPU type : 2097.710, CPU model: E12)</br> Build System Toolkit: 4.0.6 M2 (RTC-I20131211-0354), 4.0.5 GA (RTC-I20131025-2055) </td> </tr> </table> ---++ Methodology Build time and individual activity time were compared by getting test start date and time. For CPU and memory utilization monitoring tools NMON was used for RTC server and RMF on zOS was used for Rational Build Agent. The sample project for the test was Mortgage*100 which is 100 duplicates of the [[https://jazz.net/wiki/bin/view/Main/ZOSBuildSamplesV4][Mortgage sample application]] . <table class="gray-table" style="width: 40%"> <tr> <th><strong>Test Data</strong></th> <th></th> </tr> <tr> <td><strong>Sample Project</strong></td> <td>Mortgage*100</td> </tr> <tr> <td><strong>Assets</strong></td> <td>600 COBOL programs<br/> 400 Copybooks<br/> 200 BMS<br/>3 others<br/> </td> </tr> <tr> <td><strong>Total Assets</strong></td> <td>1203 </td> </tr> </table> In the repository the source code is stored in one stream with one single component which includes 4 zComponent Projects. Each test scenario is executed twice against the two versions. ---+++Test Scenarios <table class="gray-table"> <tbody> <tr> <th align="center">Test Scenario</th> <th align="center">Description</th> </tr> <tr> <td>RTC EE features</td> <td>1. Request full dependency build</br>2. Request component-based promotion, after full dependency build in step 1 with 800 files</br>3. Request package</br>4. Request deployment</td> </tr> <tr> <td>Incremental Build</td> <td>1. Change a copybook (!MortgageApplication-Common\zOSsrc\COPYBOOK\A00MTCOM.cpy) and request build</br>2. Change a COBOL file (!MortgageApplication-EPSCMORT\zOSsrc\COBOL\A00CMORT.cbl) and request build</br>3. Change all copybooks and request build</td> </tr> </tbody> </table> ---++ Results ---+++ Run duration These data tables show the run duration comparing between 4.0.6 and 4.0.5 with the test start and completion time. In the scenario of the incremental build (request build after changing all the copybook files), the total run time has an improvement about 5% , which is a result of performance improvements in incremental build preprocessing speeds of version 4.0.6. In version 4.0.6, Suppress build map links option is added to promotion definition. Before 4.0.6, build map links were automatically published to the build result (unless manually set additional build property). In 4.0.6, A new check box on the promotion definition allows you to turn this feature off, which improves processing speed. By default, new definitions will not publish build map links. <img src="%ATTACHURLPATH%/runtime_build.png" alt="runtime_build.png" width="80%" height="80%" /> <img src="%ATTACHURLPATH%/runtime_incremental.png" alt="runtime_incremental.png" width="80%" height="80%" /> <img src="%ATTACHURLPATH%/runtime_promotion.png" alt="runtime_promotion.png" width="80%" height="80%" /> <img src="%ATTACHURLPATH%/runtime_package.png" alt="runtime_package.png" width="80%" height="80%" /> ---+++ Build Activities These data tables display the detailed build activity run time. In version 4.0.6, there is performance improvements in incremental build preprocessing speeds. In the scenario of the incremental build (request build after changing all the copybook files), the "Collecting buildable files" time in preprocessing time improved about 25%. The improvements reflected the change of build map queries to adopt the Java JFS API. <img src="%ATTACHURLPATH%/activity_build.png" alt="activity_build.png" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/activity_incremental.png" alt="activity_incremental.png" width="80%" height="80%" /> <img src="%ATTACHURLPATH%/activity_promotion.png" alt="activity_promotion.png" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/activity_package.png" alt="activity_package.png" width="70%" height="70%" /> ---+++ CPU and Memory for RTC server This graph shows CPU and memory utilization for RTC server, data is collected by NMON tool. 4.0.5 and 4.0.6 show similar CPU and memory utilization. <img src="%ATTACHURLPATH%/405_server.gif" alt="405_server.gif" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/406_server.gif" alt="406_server.gif" width="70%" height="70%" /> ---+++ CPU and Memory for Build Agent This graph shows CPU and memory utilization for Build Forge Agent on ZOS machine, data is collected by RMF tool. 4.0.5 and 4.0.6 show similar CPU and memory utilization. <img src="%ATTACHURLPATH%/405_bfa.gif" alt="405_bfa.gif" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/406_bfa.gif" alt="406_bfa.gif" width="70%" height="70%" /> ---++ Appendix A - Key Tuning Parameters #AppendixA <table class="gray-table"> <tbody> <tr> <th align="left" width="200"><strong>Product</strong><br></th> <th align="left" width="100"><strong>Version</strong></th> <th align="left" width="600"><strong>Highlights for configurations under test</strong></th> </tr> <tr> <td style="vertical-align: top;">IBM !WebSphere Application Server</td> <td style="vertical-align: top;">8.0.0.3 </td> <td style="vertical-align: top;"><strong>JVM settings:</strong> * GC policy and arguments, max and init heap sizes: <verbatim> -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -Xmx4g -Xms4g</verbatim> <strong>OS configuration:</strong> <verbatim> * hard nofile 120000 * soft nofile 120000</verbatim> Refer to http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/topic/com.ibm.jazz.install.doc/topics/c_special_considerations_linux.html for details </td> </tr> <tr> <td>DB2</td> <td>DB2 Enterprise Server 9.7.0.5</td> <td>Tablespace is stored on the same machine as IBM !WebSphere Application Server</td> </tr> <tr> <td>License Server</td> <td>Same as CLM version</td> <td>Hosted locally by JTS server</td> </tr> <tr> <td>Network</td> <td> </td> <td>Shared subnet within test lab</td> </tr> </tbody> </table> ---++++!! About the authors Main.SuHui -------------------- ---+++++!! Questions and comments: * What other performance information would you like to see here? * Do you have performance scenarios to share? * Do you have scenarios that are not addressed in documentation? * Where are you having problems in performance? %COMMENT{type="below" target="PerformanceDatasheetReaderComments" button="Submit"}% %INCLUDE{"PerformanceDatasheetReaderComments"}% <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r14
<
r13
<
r12
<
r11
<
r10
|
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
.