<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 Improvement of Source Code Data Collection and Query in 5.0 %DKGRAY% Authors: [[Main.SuHui][Su Hui]]</br> Last updated: June 2, 2014 </br> Build basis: Rational Team Concert on z/OS 5.0 %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 %STARTSECTION{"Intro"}% This report compares the performance of Rational Team Concert (RTC) for z/OS of version 5.0 to the previous 4.0.6 release. The version 5.0 enhancements include performance improvements in Enterprise Extensions source code data collection service and source code data query. Source code data is collected by RTC to help find source code dependencies, which will be interrogated during dependency build. The source code data collection service is invoked both as an asynchronous daemon that runs on the Jazz Team Server, and also when a dependency build is requested. It can also be invoked manually in the Eclipse client. %ENDSECTION{"Intro"}% The test measured the performance of the source code data collection service by requesting dependency builds and by manually running in Eclipse client. In version 5.0, the speed for the source code data collection is improved significantly compared to the previous 4.0.6 release. After the source code data is collected, queries can be created to find resources with any given source code data value in the Eclipse Client. In version 5.0, enhancement is made to reduce the client side processing of source code data query time. In this test, the speeds for large source code data queries are notably faster in version 5.0 than in version 4.0.6. ---++ 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.6 to 5.0: * In the scenario of the initial enterprise build, *the preprocessing speeds are up to 49% faster*.Within preprocessing, "Updating dependency data" activity speed improved about 31%, and "Collecting buildable files" activity speed improved about 65%. * In the scenario of the build after changing all the copybook files, *the preprocessing speeds are up to 25% faster*. The "Updating dependency data" activity during preprocessing improved about 33%, and "Collecting buildable files" activity speed improved about 24%. * In the scenario of the build after changing all the COBOL files, *the preprocessing speeds are up to 37% faster*. The "Updating dependency data" activity during preprocessing improved about 41%, and "Collecting buildable files" activity speed improved about 35%. In the test of manually rescan or update source code data, *the speed is from 25% to 35% faster* in version 5.0 for different scenarios. For source code data query, according to the test result, *the query speed is from 52% to 80% faster* for different sizes of the returned query results. ---++ 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 z/OS. <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: 5.0 M3 (CALM-I20140228-2021), 5.0 M4 (CALM-I20140329-2009), 4.0.6 GA (CALM-I20140205-1923), 4 GB heap size </br> DB2: 9.7.0.5 </br> WAS: 8.5.5.1 </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: 5.0 M3 (RTC-I20140228-1725), 4.0.6 GA (RTC-I20140205-1437) </td> </tr> </table> ---++ Methodology Test run duration was compared by getting test start date and time. For CPU and memory utilization monitoring tools NMON was used for RTC server and RMF on z/OS was used for Rational Build Agent. The sample project for the test was Mortgage*1000 which is 1000 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*1000</td> </tr> <tr> <td><strong>Assets</strong></td> <td>6000 COBOL programs<br/> 4000 Copybooks<br/> 2000 BMS<br/>3 others<br/> </td> </tr> <tr> <td><strong>Total Assets</strong></td> <td>12003 </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 was executed twice against both versions. ---+++Test Scenarios <table class="gray-table"> <tbody> <tr> <th align="center">Test Scenario</th> <th align="center">Description</th> </tr> <tr> <td>Dependency Build</td> <td>1. Request full dependency build</br>2. Change all the copybooks and request build</br>3. Change all the COBOL files and request build</td> </tr> <tr> <td>Rescan/Update Source Code Data</td> <td>From Eclipse client : </br>1. Reset(rescan) source code data of one stream with Mortgage*1000 application</br>2. Change all copybook files and update source code data of the stream</br>3. Change all COBOL files and update source code data of the stream</td> </tr> <tr> <td>Source Code Data Query</td> <td>Create source code data queries on one stream with Mortgage*1000 application, add the below conditions respectively and run the queries: </br>1. fileType is 'MAIN', logicalName contains 'E'</br>2. fileType is 'MAIN'</br>3. fileType isnot 'DBD'</td> </tr> </tbody> </table> ---++ Results ---+++ Run duration ---++++ Dependency Build These data tables show the total run duration of the dependency builds comparing between 5.0 and 4.0.6 with the test start and completion time. <img src="%ATTACHURLPATH%/runduration.png" alt="runduration.png" width="80%" height="80%" /> The charts below display the run duration of build preprocessing and the individual activities "Updating dependency data", "Collecting buildable files" during preprocessing, which have gained significant improvements between 5.0 and 4.0.6. Builds are run twice against each release and the average time is taken for comparison. <img src="%ATTACHURLPATH%/preprocessing.gif" alt="preprocessing.gif" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/updependency.gif" alt="updependency.gif" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/collectfile.gif" alt="collectfile.gif" width="70%" height="70%" /> ---++++ Rescan/Update Source Code Data The charts below display the run duration when rescan or update source code data manually from Eclipse client. It shows that the speed for source code data collection service has improved in version 5.0 significantly compared with version 4.0.6. <img src="%ATTACHURLPATH%/scd_duration.png" alt="scd_duration.png" width="80%" height="80%" /> <img src="%ATTACHURLPATH%/scd_collection.gif" alt="scd_collection.gif" width="70%" height="70%" /> ---++++ Source Code Data Query The chart below displays the average source code query time with different size of the result sets. The data shows the client side processing of source code data queries has improved by up to 80% for large result sets. <img src="%ATTACHURLPATH%/scd_query.gif" alt="scd_query.gif" width="70%" height="70%" /> ---+++ Resource Utilization ---++++ CPU and Memory for RTC server This graph shows CPU and memory utilization for RTC server, data is collected by NMON tool. Tests in 5.0 environment and 4.0.6 environment show similar CPU and memory utilization. <img src="%ATTACHURLPATH%/406_server.gif" alt="406_server.gif" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/50_server.gif" alt="50_server.gif" width="70%" height="70%" /> ---++++ CPU and Memory for Build Agent This graph shows CPU and memory utilization for Build Forge Agent on z/OS machine, data is collected by RMF tool. Tests in 5.0 environment and 4.0.6 environment show similar CPU and memory utilization. <img src="%ATTACHURLPATH%/406_bfa.gif" alt="406_bfa.gif" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/50_bfa.gif" alt="50_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.5.5.1 </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>
This topic: Deployment
>
WebHome
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RationalTeamConcertOnZOSPerformance50
History: r14 - 2014-09-15 - 10:10:36 -
JorgeAlbertoDiaz
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
.