EditAttachPrintable
TWiki > Deployment Web > DeploymentFormattingGuidance > RationalTeamConcertOnZOSPerformanceImpactAfterJavaJFSAPIAdoptionIn405
Revision 5 - 2013-10-21 - 03:35:48 - Main.bjsuhui

uc.png Rational Team Concert for z/OS Performance Impact of Java JFS API Adoption In 4.0.5

Authors: SuHui
Build basis: Rational Team Concert on ZOS 4.0.5, 4.0.4

Introduction

RTC for z/OS has recently introduced a Java API to access to JFS(Jazz Foundation Services) instead of using the HTTP APIs, which provides the potential for significant performance improvements. This report compares the performance before and after RTC for z/OS adopted JAVA JFS API in part of the its resource operations and queries. Comparision is made between 4.0.5 development version and previous 4.0.4 release. The test objective is to verify the performance improvement for the new JAVA JFS API adoption.

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 before and after Java JFS API adoption for the two different versions of the Rational Team Concert product. The results shown here should thus be looked at as a comparison of the contrasting performance between the two versions, and not as an absolute benchmark of performance.

Findings

Based on the test data , The performance of the RTC for z/OS has improved significantly from 4.0.5 to 4.0.4 on some user scenarios. The promotion time improved about 20% (50% of "Generating list of binaries to promote" time and 15% of "Finalize build maps"). A build property(team.enterprise.build.dependency.forceFullAnalysis) was added during team build to reflect the impact of the changed queries , the preprocessing build time shows a improvement of about 60% which indicate a potential for performance improvements. While for other scenarios , the performance stay consistent between the two versions.

Topology

The RTC server was set up based on WebSphere and DB2 on Linux for System z. Build machine with Rational Build Agent was on zOS.

Test Environment
RTC Server Operating System : Linux for System z
System Resource : 10G Storage, 4CPs(Processor)
CLM : version 4.0.5, 4.0.4, 4G heap size
DB2 : version 9.7.0.5
WAS : version 8.0.0.2
Build Forge Agent Operating System : z/OS
System Resource : 6G Storage, 4CPs(Processor)

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 for Rational Build Agent.

The Sample Project for the test was Mortgage*100, which is a 100 duplicates of the Mortgage sample application with 800 compiles. Each test scenarios are executed twice against the two versions.

Test Scenarios

Test Scenario Description
RTC EE features 1.Request full dependency build
2.Request component-based promotion, after full dependency build in step 1 with 800 files
Incremental Build 1.Change a copybook and request build
2.Change a cobol file and request build
3.Change all copybooks and request build
Enterprise build with build property turned on to force full analysis Run enterprise build with build property team.enterprise.build.dependency.forceFullAnalysis=true
Concurrent build Change a cobol file and run 5 personal build concurrently

Results

Run duration

These data table shows the run duration comparing between 4.0.4 and 4.0.5. The build time with full analysis enabled , promotion time and the test build time after the promotion show the significant performance improvements.

The promotion time reduced about 20%. Test build time after promotion reduced by 35%. Build with team.enterprise.build.dependency.forceFullAnalysis property time reduced about 60%.

run_duration.png run_duration_concurrent.png

Build Activities

These data tables display the detailed build activity run time, improvements is contributed by "Collecting buildable files" in the build. "Generating list of binaries to promote" and "Finalize build maps" Activities are the major improvements for the promotion time. The improvements reflected the changing about build map service in RTC for z/OS which adopted the JAVA JFS API.

activity_build.png activity_build_fullanalysis.png activity_promotion.png activity_incrementalbuild.png activity_concurrent.png

CPU and Memory for RTC server

This graph show CPU and Memory utilization for RTC server, data is collected by nmon tool. 4.0.4 and 4.0.5 show similar CPU and Memory utilization.

clm_memory.png

CPU and Memory for Build Agent

This graph show CPU and Memory utilization for Build Forge Agent on ZOS machine, data is collected by RMF tool. 4.0.4 and 4.0.5 show similar CPU and Memory utilization.

BFA.png

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

Topic attachments
I Attachment Action Size Date Who Comment
Pngpng BFA.png manage 40.8 K 2013-10-18 - 05:27 UnknownUser  
Pngpng activity_build.png manage 43.1 K 2013-10-17 - 11:25 UnknownUser  
Pngpng activity_build_fullanalysis.png manage 23.1 K 2013-10-17 - 11:26 UnknownUser  
Pngpng activity_concurrent.png manage 81.0 K 2013-10-18 - 02:27 UnknownUser  
Pngpng activity_incrementalbuild.png manage 334.0 K 2013-10-17 - 11:28 UnknownUser  
Pngpng activity_promotion.png manage 47.8 K 2013-10-17 - 11:30 UnknownUser  
Pngpng clm_memory.png manage 228.3 K 2013-10-18 - 05:26 UnknownUser  
Pngpng run_duration.png manage 230.2 K 2013-10-17 - 10:55 UnknownUser  
Pngpng run_duration_concurrent.png manage 45.8 K 2013-10-17 - 11:46 UnknownUser  
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r27 | r7 < r6 < r5 < r4 | More topic actions...
This site is powered by the TWiki collaboration platformCopyright © 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.