<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/todo.png" alt="todo.png" width="50" height="50" align="right"> Rational Team Concert for System z sizing report: RTC 4.0.4 release %DKGRAY% Authors: Main.LuYuliang<br> Build basis: Rational Team Concert 4.0.4 %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 article provides the Rational Team Concert 4.0.4 sizing report specifically for z/OS, which is part of findings for [[https://jazz.net/wiki/bin/view/Deployment/RTCSystemZPerformanceTesting][RTC for System z performance testing]]. We are adopting the Rational Team Concert test harness to simulate actual client workload and validate our scalability requirements. Read the [[https://jazz.net/wiki/bin/view/Deployment/RationalTeamConcert404PerformanceReport][Collaborative Lifecycle Management performance report: RTC 4.0.4 release]] first for more information about the Rational Team Concert test harness. Since version 4.0 was released, we have focused on performance testing using [[https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview][standard topologies]]. For more information related to the system requirements, see [[https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements][System Requirements for Collaborative Lifecycle Management]]. ---+++!! Disclaimer %INCLUDE{"PerformanceDatasheetDisclaimer"}% ---++ Topology This sizing report is specifically for: * Single-Tier Mode: Linux for System z standalone topology, which deploys the application server on Linux for System z and DB2 on Linux for System z <img src="%ATTACHURLPATH%/Enterprise_zOS_WAS_DB2_on_Linux_z_topology.png" alt="Enterprise_zOS_WAS_DB2_on_Linux_z_topology.png" width="711" height="443" /> * Dual-Tier Mode: [[https://jazz.net/wiki/bin/view/Deployment/AlternativeCLMDeploymentTopologies#CLM_E5_Enterprise_zOS_Linux_on_S][standard topology - E5]], which deploys the application server on Linux for System z and DB2 on z/OS <img src="%ATTACHURLPATH%/Enterprise_zOS_Linux_on_z_DB2_z_topology.png" alt="Enterprise_zOS_Linux_on_z_DB2_z_topology.png" width="711" height="443" /> ---++ Findings ---+++ Small-scale enterprise deployment For this sizing report, a small-scale deployment is a configuration of between 100 and 700 users on either a single-tier or a double-tier setup. For a single-tier setup, the application server and database are running on the same LPAR. For dual-tier setup, the application server and database are running on different LPARs. * The following table lists the system configurations we used for a small-scale single-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server and database - Linux for System z (single-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>SUSE Linux Enterprise Server 10 (S390x)</td> </tr> <tr> <td style="width:300px;">Application server</td> <td>WebSphere Application Server Network Deployment v8.0.0.3</td> </tr> <tr> <td style="width:300px;">Database</td> <td>DB2 9.7.0.5</td> </tr> </tbody> </table> * The following table lists the system configurations we recommend for a small-scale single-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server and database - Linux for System z (single-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>1700 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>6 GB or higher</td> </tr> </tbody> </table> * The following tables list the system configurations we used for a small-scale dual-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server - Linux for System z (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>SUSE Linux Enterprise Server 10 (S390x)</td> </tr> <tr> <td style="width:300px;">Application server</td> <td>WebSphere Application Server Network Deployment v8.0.0.3</td> </tr> </tbody> </table> <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Database - IBM System z10 (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>z/OS 1.12</td> </tr> <tr> <td style="width:300px;">Database</td> <td>DB2 on z/OS v10.1</td> </tr> </tbody> </table> * The following tables list the system configurations we recommend for a small-scale dual-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server - Linux for System z (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>1700 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>6 GB or higher</td> </tr> </tbody> </table> <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Database - IBM System z10 (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>200 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>6 GB or higher</td> </tr> </tbody> </table> ---+++ Large-scale enterprise deployment For this sizing report, a large-scale deployment is a configuration of between 700 and 2000 users on either a single-tier or a double-tier setup. For a single-tier setup, the application server and database are running on the same LPAR. For dual-tier setup, the application server and database are running on different LPARs. * The following table lists the system configurations we used for a large-scale single-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server and database - Linux for System z (single-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>SUSE Linux Enterprise Server 10 (S390x)</td> </tr> <tr> <td style="width:300px;">Application server</td> <td>WebSphere Application Server Network Deployment v8.0.0.3</td> </tr> <tr> <td style="width:300px;">Database</td> <td>DB2 9.7.0.5</td> </tr> </tbody> </table> * The following table lists the system configurations we recommend for a large-scale single-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server and database - Linux for System z (single-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>2700 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>10 GB or higher</td> </tr> </tbody> </table> * The following tables list the system configurations we used for a large-scale dual-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server - Linux for System z (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>SUSE Linux Enterprise Server 10 (S390x)</td> </tr> <tr> <td style="width:300px;">Application server</td> <td>WebSphere Application Server Network Deployment v8.0.0.3</td> </tr> </tbody> </table> <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Database - IBM System z10 (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>z/OS 1.12</td> </tr> <tr> <td style="width:300px;">Database</td> <td>DB2 on z/OS v10.1</td> </tr> </tbody> </table> * The following tables list the system configurations we recommend for a large-scale dual-tier setup scenario: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Application server - Linux for System z (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>2700 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>10 GB or higher</td> </tr> </tbody> </table> <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Database - IBM System z10 (dual-tier configuration)</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>300 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>6 GB or higher</td> </tr> </tbody> </table> ---+++ Rational Build Agent The Rational Build Agent is required for System z builds. We are running benchmark testing to achieve the data. Read [[https://jazz.net/wiki/bin/view/Deployment/RationalTeamConcertForZOSPerformanceComparisonBetweenReleases][Rational Team Concert For z/OS Performance Comparison Between Releases ]] for more information. * The following table lists the system configurations we used for the Rational Build Agent: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Rational Build Agent on IBM System z/OS</b></th> </tr> <tr> <td style="width:300px;">Disk</td> <td>DS8000 with PAV enabled</td> </tr> <tr> <td style="width:300px;">Operating System</td> <td>z/OS 1.12</td> </tr> <tr> <td style="width:300px;">Database</td> <td>DB2 on z/OS v10.1</td> </tr> </tbody> </table> * The following table lists the system configurations we recommend for the Rational Build Agent: <table class="gray-table"> <tbody> <tr> <th valign="top" colspan='2'> <b>Rational Build Agent on IBM System z/OS</b></th> </tr> <tr> <td style="width:300px;">CPU</td> <td>100 mips or higher</td> </tr> <tr> <td style="width:300px;">Memory</td> <td>2 GB or higher</td> </tr> </tbody> </table> ---++ Appendix A - WebSphere Configuration #AppendixA <table class="gray-table"> <tbody> <tr> <td style="vertical-align: top;">IBM WebSphere Application Server Network Deployment</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> * Small business scale: -Xmx4g -Xms4g -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 * Large business scale: -Xmx6g -Xms6g -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 </verbatim> *Thread pools:* * Maximum !WebContainer = 50 * Minimum !WebContainer = 50 *OS Configuration:* Increase system wide resources for the app server process owner: * max user processes = 40249 * core file size = unlimited * open files = 120000 * stack size = 8192 </td> </tr> <tr> <td>DB2</td> <td>DB2 on z/OS v10.1</td> <td></td> </tr> <tr> <td>License server</td> <td>Same as CLM version</td> <td>Hosted locally by JTS server</td> </tr> <tr> <td>RPT workbench</td> <td>8.2.1.5</td> <td>Defaults</td> </tr> <tr> <td>RPT agents</td> <td>8.2.1.5</td> <td>Defaults</td> </tr> <tr> <td>Network</td> <td> </td> <td>Shared subnet within test lab</td> </tr> </tbody> </table> ---++ Appendix B - History #AppendixB * [[https://jazz.net/library/article/816][Rational Team Concert 4.x sizing report for z/OS]] * [[https://jazz.net/library/article/605][Rational Team Concert 3.0 sizing guide for z/OS]] ---++ Related Links: * [[Rtceeperftestresultrootpage][RTC EE performance datasheets and sizing reports]] ---++++!! About the authors Main.LuYuliang is has been a Software Engineer at IBM for over 3 years. He is part of the Rational Performance Engineering group. -------------------- ---+++++!! 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
>
PerformanceDatasheets
>
RationalTeamConcert404PerformanceReportforSystemZ
History: r6 - 2014-04-01 - 18:28:17 - Main.gcovell
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
.