<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 IBM Features Performance Comparison Between Releases %DKGRAY% Authors: Lu Lu, Zhang Wei</br> Date: June 30th, 2015 </br> Build basis: Rational Team Concert for z/OS from 5.0.2, 6.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 This report compares the performance of RTC for IBMi features(Package, Deploy and Promotion) between releases since v5.0.2 until v6.0. Generally constant performance improvements are made into releases of RTC for IBMi. The objective of this report is to present the improvements. The performance data provided is obtained by benchmark test of each release. Currently the report includes only the build information. ---++ Disclaimer %INCLUDE{"PerformanceDatasheetDisclaimer"}% ---++ Findings Based on following feature test data, we can get following summaries of RTC EE features from 5.0.2 to 6.0: 1. Performance of 'Promotion' feature has improved significantly (<strong>76%</strong>) from v5.0.2 to v6.0. 2. Performance of 'Deploy' feature has improved slightly. 3. Performance of 'Package' feature is stable. From 5.0.2 to 6.0, the overall performance improvement of the Promotion feature is about 76%:<br/> <strong><br/> *From 5.0.2 to 6.0, promotion time has improved by 80% <br/> - 'Generating list of binaries to promote' activity is the most notable improvement of 80% in v6.0.<br/> - 'Promote' activity is improved of 62% in v6.0.<br/> - 'Finalize build maps' is improved of 93% in v6.0. <br/> </strong> ---++ Topology The tests are executed in a Single Tier Topology infrastructure like the one in the following diagram: %INCLUDE{"RTCEETestingTopologies" section="SingleTierI"}% The RTC server was set up based on !WebSphere and DB2 on IBMi. The build machine with Rational Build Agent was on IBMi. <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: IBMi v7.1</br> System Resource : 4 dedicated processors, 30GB memory </br> CLM: from 6.0 GA, 4 GB heap size </br> DB2: DB2 for IBMi v7.1</br> WAS: 8.5.5.3 (from 5.0.2 GA to 6.0GA)</br> </td> <tr> <td><strong>Build Forge Agent</strong></td> <td>Operating System & Version: IBMi v7.1</br> System Resource: 4 dedicated processors, 30GB memory</br> Build System Toolkit: from 5.0.2 GA to 6.0GA </td> </tr> </table> ---++ Methodology Build time and individual activity time are compared by getting test start date and time. The sample projects for the test are: * Maillist Application *100 * Maillist Application *1000 <table class="gray-table" style="width: 60%"> <tr> <th><strong>Test Data</strong></th> <th></th> <th></th> </tr> <tr> <td><strong>Sample Project</strong></td> <td>Maillist *100</td> <td>Maillist *1000</td> </tr> <tr> <td><strong>Assets</strong></td> <td>500 RPGLE<br/> 200 SRVPGM<br/> 100 PGMSRC<br/> 4 DSPF<br/> 4 LF <br/> 2 PF <br/> 6 CLLE <br/> 1 * CLP <br/> </td> <td>5000 RPGLE<br/> 2000 SRVPGM<br/> 1000 PGMSRC<br/> 4 DSPF<br/> 4 LF <br/> 2 PF <br/> 6 CLLE <br/> 1 * CLP <br/> </td> </tr> <tr> <td><strong>Total Assets</strong></td> <td>817 </td> <td>8017 </td> </tr> </table> In the repository the source code is stored in one stream with one single component. Enterprise builds are executed twice against each version. ---++ Results ---+++ Run duration Below charts show run duration comparing between 5.0.2 until 6.0 of each EE feature, and each feature of EE are run twice against each release and the average time is taken for comparison. <b>Package:</b></br> From below 'Package' feature runtime chart, each release has similar runtime duration, no big improvement in this feature, but this feature is stable. <img src="%ATTACHURLPATH%/packageRuntime.gif" alt="package_runtime.jpg" width="70%" height="70%" /> <br/> <b>Deploy:</b><br/> From below 'Deploy' feature runtime chart, it consistent from v5.0.2 to v6.0. <br/> <img src="%ATTACHURLPATH%/deployRuntime.gif" alt="deploy_runtime.jpg" width="70%" height="70%" /> <br/> <b>Promotion:</b><br/> From below 'Promotion' feature runtime chart, this feature is continuous improved release by release, it has been improved <strong>80%</strong>. For the release by release comparison, it improved by 80% from 5.0.2 to 6.0. <img src="%ATTACHURLPATH%/promotionRuntime.gif" alt="promotion_runtime.jpg" width="70%" height="70%" /> <img src="%ATTACHURLPATH%/promotionRuntime2.gif" alt="promotion_runtime_withChangeSet.jpg" width="70%" height="70%" /> <br/> ---+++ Build Activities Display all feature test results in one comparison table is too large, so separate into 3 comparison tables and link to other page. For EE feature test results, they are divided into following 3 comparison tables, please navigate to linked page for detailed results. <strong><red>'Package' Comparison Results [[RTCEEFeaturesPackageComparisonForIBMi][here]]</red></strong> <strong>'Deploy' Comparison Results [[RTCEEFeaturesDeployComparisonForIBMi][here]]</strong> <strong>'Promotion(Full Promotion and Single Changeset)' Comparison Results [[RTCEEFeaturesPromotionComarisonForIBMi][here]]</strong> The chars below display the run times of build activity "Collecting buildable files" and "Compile" which have gained some improvements between releases. Builds are run twice against each release and the average time is taken for comparison. ---++ 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.3 (5.0.2GA to 6.0GA)</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> </td> </tr> <tr> <td>DB2</td> <td>DB2 Enterprise Server for IBMi v7.1 (5.0.2GA to 6.0GA)</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.Lu Lu -------------------- ---+++++!! 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
>
RTCSystemZPerformanceTesting
>
RTCEEBenchmarkTests
>
RTCEEFeaturePerformanceComparisonBetweenReleasesForIBMi
History: r1 - 2015-06-30 - 06:15:18 -
LuLu
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
.