Rational Team Concert for System z sizing report: RTC 5.0 release

Introduction

We focused on performance testing using standard topologies. For more information related to the system requirements, see System Requirements in the Installing, Upgrading and Migrating section.

Disclaimer

The information in this document is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites. Any performance data contained in this document was determined in a controlled environment, and therefore, the results that may be obtained in other operating environments may vary significantly. Users of this document should verify the applicable data for their specific environment.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multi-programming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

This testing was done as a way to compare and characterize the differences in performance between different versions of the product. The results shown here should thus be looked at as a comparison of the contrasting performance between different versions, and not as an absolute benchmark of performance.

What our tests measure

We use predominantly automated tooling such as Rational Performance Tester (RPT) to simulate a workload normally generated by client software such as the Eclipse client or web browsers. All response times listed are those measured by our automated tooling and not a client.

The diagram below describes at a very high level which aspects of the entire end-to-end experience (human end-user to server and back again) that our performance tests simulate. The tests described in this article simulate a segment of the end-to-end transaction as indicated in the middle of the diagram. Performance tests are server-side and capture response times for this segment of the transaction.

Topology

• 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

• Dual-Tier Mode: standard topology - E5, which deploys the application server on Linux for System z and DB2 on z/OS

Findings

Small-scale enterprise deployment

• The following table lists the system configurations we used for a small-scale single-tier setup scenario:

  Application server and database - Linux for System z (single-tier configuration)
  Disk	DS8000 with PAV enabled
  Operating System	SUSE Linux Enterprise Server 10 (S390x)
  Application server	WebSphere Application Server Network Deployment v8.5.5.1
  Database	DB2 10.1

• The following table lists the system configurations we recommend for a small-scale single-tier setup scenario:

  Application server and database - Linux for System z (single-tier configuration)
  CPU	1400 mips or higher
  Memory	6 GB or higher

• The following tables list the system configurations we used for a small-scale dual-tier setup scenario:

  Application server - Linux for System z (dual-tier configuration)
  Disk	DS8000 with PAV enabled
  Operating System	SUSE Linux Enterprise Server 10 (S390x)
  Application server	WebSphere Application Server Network Deployment v8.5.5.1

  Database - IBM System z10 (dual-tier configuration)
  Disk	DS8000 with PAV enabled
  Operating System	z/OS 1.12
  Database	DB2 on z/OS v10.1

• The following tables list the system configurations we recommend for a small-scale dual-tier setup scenario:

  Application server - Linux for System z (dual-tier configuration)
  CPU	1200 mips or higher
  Memory	6 GB or higher

  Database - IBM System z10 (dual-tier configuration)
  CPU	200 mips or higher
  Memory	6 GB or higher

Large-scale enterprise deployment

• The following table lists the system configurations we used for a large-scale single-tier setup scenario:

  Application server and database - Linux for System z (single-tier configuration)
  Disk	DS8000 with PAV enabled
  Operating System	SUSE Linux Enterprise Server 10 (S390x)
  Application server	WebSphere Application Server Network Deployment v8.5.5.1
  Database	DB2 10.1

• The following table lists the system configurations we recommend for a large-scale single-tier setup scenario:

  Application server and database - Linux for System z (single-tier configuration)
  CPU	2700 mips or higher
  Memory	10 GB or higher

• The following tables list the system configurations we used for a large-scale dual-tier setup scenario:

  Application server - Linux for System z (dual-tier configuration)
  Disk	DS8000 with PAV enabled
  Operating System	SUSE Linux Enterprise Server 10 (S390x)
  Application server	WebSphere Application Server Network Deployment v8.5.5.1

  Database - IBM System z10 (dual-tier configuration)
  Disk	DS8000 with PAV enabled
  Operating System	z/OS 1.12
  Database	DB2 on z/OS v10.1

• The following tables list the system configurations we recommend for a large-scale dual-tier setup scenario:

  Application server - Linux for System z (dual-tier configuration)
  CPU	2500 mips or higher
  Memory	10 GB or higher

  Database - IBM System z10 (dual-tier configuration)
  CPU	400 mips or higher
  Memory	6 GB or higher

Rational Build Agent

• The following table lists the system configurations we used for the Rational Build Agent:

  Rational Build Agent on IBM System z/OS
  Disk	DS8000 with PAV enabled
  Operating System	z/OS 1.12
  Database	DB2 on z/OS v10.1

• The following table lists the system configurations we recommend for the Rational Build Agent:

  Rational Build Agent on IBM System z/OS
  CPU	100 mips or higher
  Memory	2 GB or higher

Note : The System z Integrated Information Processor (zIIP) can help to offload application workload (Java application) from z/OS greatly. We recommend to run with a zIIP processor on the build machine in order to offload the java workload and lower the overall cost. For detailed information, please refer to Rational Team Concert Enterprise Extension zIIP Offload Performance in 5.0.

Appendix A

   * Small business scale:
-Xmx4g -Xms4g -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000
   * Large business scale:
-Xmx6g -Xms6g -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000

Appendix B - History

• Rational Team Concert for System z sizing report: RTC 4.0.4 release
• Rational Team Concert 4.x sizing report for z/OS
• Rational Team Concert 3.0 sizing guide for z/OS

Related Links:

• RTC EE performance datasheets and sizing reports

About the authors

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?

Warning: Can't find topic Deployment.PerformanceDatasheetReaderComments