IBM Rational ClearCase Remote Client Version 7.1 Performance Report (Windows)

Size: px

Start display at page:

Download "IBM Rational ClearCase Remote Client Version 7.1 Performance Report (Windows)"

Jack Johnathan Jordan
5 years ago
Views:

1 IBM Rational ClearCase Remote Client Version 7.1 Performance Report (Windows) This report compares Rational ClearCase Remote Client (CCRC) server performance and scalability for the and 7.1 releases. Rational ClearCase and ClearQuest 7.1 releases introduce the Change Management (CM) Server, which provides server-side support for Wide Area Network (WAN) interfaces to Rational ClearCase and Rational ClearQuest. CM Server is a unified application server for both CCRC and ClearQuest Web. It leverages the performance, security and scalability of WebSphere Application Server (version ). For detailed information regarding CM server architecture, deployment and administration, please refer to Rational ClearCase 7.1 information center. CM server is also referred as CCRC server in this performance report. NOTE: Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments might vary significantly. Users of this document should verify the applicable data for their specific environment. Test Environment and Configuration A series of tests were conducted to measure performance and scalability. The first set of tests measure CCRC server response times under a single-user and 100 user load for both Rational ClearCase and 7.1 releases. The second set of tests measure Rational ClearCase 7.1 CM server response times for user loads ranging from 50 to 200 users. The simulated ClearCase test environment consisted of two Unified Change Management (UCM) projects that shared the same component Version Object Base (VOB). All the tests were performed in a test network environment with a 100 milliseconds round-trip latency and a 3Mbps duplex bandwidth between the test driver system (acting as a CCRC client system) and the CCRC server using non- SSL connection. Network connectivity between CCRC server, VOB server and Windows domain controller was unconstrained and operated at full 100 Mbps fast-ethernet bandwidth with no latency (see Figure 1). Figure 1: Test configuration and network diagram The test hardware used for testing was as follows: Test Drivers Two IBM System x3550 with dual 3.4 GHz Intel Xeon CPUs, 2 GB memory, operating system: Microsoft Windows 2003 Server Standard Edition with service pack 1. WAN Simulator Dell Precision 340 with one 1.4 GHz Intel Pentium 4 CPU, 512 MB memory, operating system: FreeBSD 4.7. CM Server IBM System x3850 with four 3.67 GHz Intel Xeon CPUs, 8 GB memory, operating system: Microsoft Windows 2003 Server Enterprise Edition with service pack 1 VOB Server IBM System x3850 with four 3.67 GHz Intel Xeon CPUs, 8 GB memory, operating system: Microsoft Windows 2003 Server Enterprise Edition with service pack 1 Domain Controller Dell Precision 340 with one 1.4 GHz Intel Pentium 4 CPU, 512 MB memory, operating system: Microsoft Windows 2000 advanced server, service pack 4 Windows CM Server Tuning for Performance & Scalability

As a WebSphere Application Server based J2EE server, CM server requires well thought-out performance tuning to optimize performance and scalability.

2 As a WebSphere Application Server based J2EE server, CM server requires well thought-out performance tuning to optimize performance and scalability. The following changes shown in Table 1 were made after installing CM server on Windows 2003 server (32-bit) platform. Make sure the Allow service to interact with desktop heap checkbox is checked in the properties of the Windows service for IBM WebSphere Application Server V6.1 cmprofile, as shown in the graph below. Table 1: Changes made on CM server and VOB server for the CCRC scalability tests WAS 6.1 Settings on the CM Server JVM heap size of the application server Default thread pool of the application server "Web container" thread pool of the application server CM Server MBean Settings serverthresholdcount 200 maxservercount 300 Windows registry setting on CM server *SessionViewSize *Non-interactive heap size Windows registry setting on VOB server min=1024 MB, max=1024 MB min=200, max=400 min=200, max= MB (default is 48 MB on Windows 2003 server, 32 bit) 1024 KB (default is 512 KB on Windows 2003 server, 32 bit) LockMgrCmdLine -a almd -f u q 4096 * See the following IBM tech note for details regarding Windows desktop heap. It s recommended to restart CM server after making any changes for performance tuning. Transaction Details IBM Rational Performance Tester (RPT) is the performance test tool used to simulate virtual CCRC users. Using RPT custom code, Java scripts access the CCRC API for each virtual user and execute CCRC transactions (see list of transactions that follows). During test execution, RPT collects data on the server response times for individual transactions. The test environment uses a component VOB (1.82 GB in size) containing 43,650 directories and 151,306 files. During the test, a directory that contains 53 folders and 467 files (3.41 MB in size) was loaded and updated from the server during LoadView and UpdateView testing. All transactions are executed in a RPT performance schedule for 50 iterations. Test results were averages of the 50 sample points. In this environment, RPT measures the CCRC server response times for the following transactions: Table 2: CCRC transactions MkStream CreateView LoadView MakeActivity MakeFolder CheckoutFolder CheckinFolder MakeFile Create a UCM development stream Create a CCRC Web view Set config spec, and load source directory in a view Create a UCM activity Create a new directory folder and add it to source control Check-out a directory element Check-in a directory element Create a new file and add it to source control

CheckoutFile Check-out existing file; file sizes 6 KB CheckinFile Check-in an existing file; file sizes 6 KB LsHisory List the version history of a file GetActProperties Get the properties of the

3 CheckoutFile Check-out existing file; file sizes 6 KB CheckinFile Check-in an existing file; file sizes 6 KB LsHisory List the version history of a file GetActProperties Get the properties of the currently set UCM activity GetViewProperties Get the properties of the current working view UpdateView Update current working view with the server RemoveView Remove an existing CCRC view Figure 2 below shows the relative distribution of the above transactions used for multi-user testing. Findings: Figure 2: CCRC Work-load Transaction Mix These test results are specific to the product software, test configuration, workload and environment that were used. Product performance in other environments or conditions might be different compared to the data reported in this document. Figures 3 and 4 show the single-user benchmark (SUB) and 100 user CCRC server response times under the test conditions previously described for Rational ClearCase and 7.1 releases. Figure 3: CCRC API single user performance comparison of the and 7.1 releases.

Figure 4: CCRC API 100 user performance comparison of the 7.0.1 and 7.1 releases. Overall, Rational ClearCase 7.1 CCRC API performance has improved relative to that of 7.0.1, with all of the transactions measured having comparable or improved (shorter) server response times in both single user and 100 user benchmark tests.

4 Figure 4: CCRC API 100 user performance comparison of the and 7.1 releases. Overall, Rational ClearCase 7.1 CCRC API performance has improved relative to that of 7.0.1, with all of the transactions measured having comparable or improved (shorter) server response times in both single user and 100 user benchmark tests. These performance improvements are attributed to the new CM server architecture, improved performance of CCRC API in WAN environment, and improvements in core ClearCase, such as the registry server performance improvements. Multi-user performance and scalability During the development cycle, iterative scalability performance testing helped development track progress and areas of improvement. See the graph below for the results of these efforts (scalability response for 50, 100, 150 and 200 simulated users). Please note that multi-user scalability tests were executed at a transaction rate for each user of 15 transactions per hour (typical developer scenario). Figure 5 is a scalability graph showing CM server response times for 50,100, 150 and 200-user load scenarios Figure 5: ClearCase 7.1 CCRC transaction response times with 50, 100 and 200 simulated users. Performance of most CCRC transactions, except LoadView and UpdateView, scaled very well as user load increased from 50 to 200. The increased transactions times for LoadView and UpdateView transactions from 50 user to 200 users were a result of the bandwidth restrictions of the WAN connection between the test drivers and the CM server. Conclusions: Based on the test results, there was a 10% or more performance improvement for CCRC transactions measured in these set of tests using Rational ClearCase 7.1 CM server over CCRC server in single user and 100 user API benchmark tests on Windows platform. In order to optimize CM server scalability performance under large user load, performance tuning on CM server is required. For hardware planning, we recommend server systems with at least four CPU cores and 4 GB memory for CM server deployment on Windows platform.

5 Legal Notices Copyright IBM Corporation 2008 All Rights Reserved. Dell and Precision are registered trademarks of Dell Inc. in the United States, other countries or both. Java is a registered trademark of Sun Microsystems Incorporated in the United States, other countries or both. IBM, Rational, ClearCase, ClearQuest, Rational Performance Tester, and System x are trademarks of International Business Machines Corporation in the United States, other countries or both. Intel, Pentium and Xeon are registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries or both. FreeBSD is a registered trademark of The FreeBSD Foundation in the United States, other countries or both. Windows is a registered trademark of Microsoft Corporation in the United States, other countries or both. Other company, product or service names may be the trademarks or service marks of others.

A Rational software Whitepaper 05/25/03. IBM Rational Rapid Developer Scalability and Performance Benchmark

A Rational software Whitepaper 05/25/03 IBM Rational Rapid Developer Scalability and Performance Benchmark 1 Executive Summary This document describes a performance benchmark for Rational s estore application