(r3) PerformanceImpactOfCombiningRMMandRTCServers < Deployment

Engineering Lifecycle Management Wiki - Deployment
Community information and contribution guidelines
~~EditAttach~~Printable
TWiki > Deployment Web > DeploymentPlanningAndDesign > PerformanceDatasheetsAndSizingGuidelines > PerformanceImpactOfCombiningRMMandRTCServers
Revision 3 - 2020-02-05 - 20:30:23 - Main.cystrunk
<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%">
<!--
   * Set ALLOWTOPICCHANGE = Main.TWikiDeploymentDatasheetsAuthorsGroup, Main.TWikiAdminGroup, Main.GrantCovell 
-->
---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right">Performance impact of combining Rational Model Manager and Rational Team Concert servers</br>
%DKGRAY% Authors: Main.SentellaCystrunk</br>
Build basis: Enterprise Lifecycle Management 7.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 is the intro

---+++!! Disclaimer

%INCLUDE{"PerformanceDatasheetDisclaimerEndToEnd"}%

---++ Summary of performance results



---++ Appendix A:  Topology


<table class="gray-table">
	<tbody>
		<tr>
			<th valign="top">Function</th>
			<th valign="top">Number of Machines</th>
			<th valign="top">Machine Type</th>
			<th valign="top">CPU / Machine</th>
			<th valign="top">Total # of CPU vCores/Machine</th>
			<th valign="top">Memory/Machine</th>
			<th valign="top">Disk</th>
			<th valign="top">Disk capacity</th>
			<th valign="top">Network interface</th>
			<th valign="top">OS and Version</th>
		</tr>
		<tr>
			<td>Oracle DB Server</td>
			<td>1</td>
			<td>Physical</td>
			<td></td>
			<td>40</td>
			<td>64G RAM</td>
			<td></td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server 7.6</td>
		</tr>
		<tr>
			<td>EWM + RMM Combined Server</td>
			<td>1</td>
			<td>Physical</td>
			<td></td>
			<td>24</td>
			<td>32G RAM<br>8G Heap</td>
			<td></td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server 6.10</td>
		</tr>
		<tr>
			<td>JTS Server</td>
			<td>1</td>
			<td>VMware VM</td>
			<td>2 x Intel Xeon E5-2665 2.4GHz (dual-core)</td>
			<td>4</td>
			<td>16G RAM<br>8G Heap</td>
			<td>N/A</td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server 7.1</td>
		</tr>
		<tr>
			<td>Jazz Authoriztion Server</td>
			<td>1</td>
			<td>VMware VM</td>
			<td>2 x Intel Xeon E5-2665 2.4GHz (dual-core)</td>
			<td>4</td>
			<td>16G</td>
			<td></td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server 7.1</td>
		</tr>
		<tr>
			<td>LDAP Server</td>
			<td>1</td>
			<td>VMware VM</td>
			<td>N/A</td>
			<td>N/A</td>
			<td>N/A</td>
			<td>N/A</td>
			<td>N/A</td>
			<td>Gigabit Ethernet</td>
			<td>N/A</td>
		</tr>
		<tr>
			<td>IHS Server</td>
			<td>1</td>
			<td>VMware VM</td>
			<td>2 x Intel Xeon E5-2698 2.3GHz</td>
			<td>4</td>
			<td>16G</td>
			<td>N/A</td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server 7.6</td>
		</tr>
		<tr>
			<td>RTC Developer Agents</td>
			<td>5</td>
			<td>VMware VM</td>
			<td>2 x Intel Xeon E5-2698 2.3GHz (dual-core)</td>
			<td>4</td>
			<td>16G</td>
			<td>N/A</td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server 7.1</td>
		</tr>
		<tr>
			<td>RMM Designer Agents</td>
			<td>5</td>
			<td>VMware VM</td>
			<td>2 x Intel Xeon E5-2698 2.3GHz (dual-core)</td>
			<td>4</td>
			<td>16G</td>
			<td>N/A</td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Windows Server Enterprise 2016</td>
		</tr>
		<tr>
			<td>Rhapsody Designer Agents</td>
			<td>1</td>
			<td>VMware VM</td>
			<td>2 x Intel Xeon E5-2698 2.3GHz (dual-core)</td>
			<td>4</td>
			<td>16G</td>
			<td>N/A</td>
			<td></td>
			<td>Gigabit Ethernet</td>
			<td>Windows Server Enterprise 2016</td>
		</tr>
	</tbody>
</table>

N/A: Not applicable.
vCores = Cores with hyperthreading


---+++ Network connectivity

All server machines and test clients are located on the same subnet. The LAN has 1000 Mbps of maximum bandwidth and less than 0.3 ms latency in ping.

---+++ Data volume and shape



---++ Appendix B:  Methodology
 
The test methodology involved collecting the standard one-hour performance test data using 1,000 concurrent users, repeating the test, and comparing the results.

Rational Performance Tester (RPT) was used to simulate the workload created using the web client.  Each user completed a random use case from a set of
available use cases.  A Rational Performance Tester script is created for  each use case. The scripts are organized by pages and each page represents a user action.
The work load is role based as each of the areas defined under sequence of actions are separated into individual user groups within an RPT schedule.

The [[#User_roles_test_cases_and_worklo][User roles, test cases and workload characterization]] section describes the configuration of the RPT schedule.

---+++ User roles, test cases and workload characterization
*User Roles*
#UserRoles
<table class="gray-table">
	<tbody>
		<tr>
			<th align="center" height="40"><b>Use role</b></th>
			<th align="center" height="40"><b>% of Total</b></th>
			<th align="center" height="40"><b>Related Actions</b></th>
		</tr>
		<tr>
			<td>QE Manager</td>
			<td align="center">8</td>
			<td>Create test plan, Browse test plans and test cases, Browse test script, Simple test plan copy, Search defect, View dashboard</td>
		</tr>
		<tr>
			<td>Test Lead</td>
			<td align="center">19</td>
			<td>Edit test environment, Edit test plan, Create test case, Bulk edit of test cases, Browse test script, Test Execution, Search defect, Edit test suite</td>
		</tr>
		<tr>
			<td>Tester</td>
			<td align="center">68</td>
			<td>Create defect, Modify defect, Search defect, Edit test case, Create test script, Edit test script, Test Execution, Browse test execution record, Browse test case result, Browse test suite result</td>
		</tr>
		<tr>
		        <td>Dashboard Viewer</td>
			<td align="center">5</td>
			<td>View dashboard(with login and logout)</td>
		</tr>
	</tbody>
</table>

---++ Appendix C:  Detailed performance results

#DetailedResults

---+++ Median page response time breakdown
#MedianRespTime
In the response time charts that follow, the unit is in milliseconds.  When interpreting the data, smaller is better.

#BrowseTestCaseExecutionRecords Browse Test Case Execution Records

<img src="%ATTACHURLPATH%/browseTERs.png" />

[[#TestCases][Back to Test Cases & workload characterization]]



---+++ RPT network transfer
<img src="%ATTACHURLPATH%/RPT_network.png" />

---+++ Resource utilization

%TABLE{ sort="off" headerbg="#3399FF" cellpadding="2" cellspacing="2" dataalign="center" caption="OS Resource Utilization - Overview" tableborder="2" tableframe="border" tablerules="none"}%
|CPU|<img src="%ATTACHURLPATH%/CPU.png" />|
|Disk|<img src="%ATTACHURLPATH%/Disk.png" />|
|Memory|<img src="%ATTACHURLPATH%/Memory.PNG" />|
|Network|<img src="%ATTACHURLPATH%/Network.PNG" />|

---+++ Garbage collection - JVM GC Charts
For JVM parameters, please refer to [[#Appendix_D_Key_configuration_par][Appendix D: Key configuration parameters]].

Verbose garbage collection (GC) is enabled by default to log the GC activities.  Below is one example of the output from the GC log for each application.

%TABLE{ sort="off" headerbg="#3399FF" cellpadding="2" cellspacing="2" dataalign="center" caption="WAS Liberty JVM Garbage Collection Charts for RQM and JTS Servers" tableborder="2" tableframe="border" tablerules="none"}%
|QM|<img src="%ATTACHURLPATH%/GC_QM_Run1.png" />|
|JTS|<img src="%ATTACHURLPATH%/GC_JTS_Run1.png" />|


---++ Appendix D:  Key configuration parameters

<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="400"><strong>Highlights for configurations under test</strong></th>
		</tr>
		<tr>
			<td style="vertical-align: top;">HAProxy</td>
			<td style="vertical-align: top;">1.5.18</td>
			<td style="vertical-align: top;">HAProxy functions as a reverse proxy server.

Configuration details can be found from the [[http://haproxy.1wt.eu/download/1.4/doc/configuration.txt][HAProxy Configuration Manual]].

*haproxy.cfg*:

   * timeout http-request    20s
   * timeout connect         20s
   * timeout client          5m
   * timeout server          5m

*OS Configuration*:

   * max user processes = 65536
      </td>
		</tr>
		<tr>
			<td style="vertical-align: top;">IBM !WebSphere Application Server Liberty</td>
			<td style="vertical-align: top;">18.0.0.3</td>
			<td style="vertical-align: top;"><strong>JVM settings:</strong>

   * Memory settings specified in server.startup before line <strong>export JAVA_OPTS</strong>:

				<verbatim>
JAVA_OPTS="$JAVA_OPTS -Xmx8g"
JAVA_OPTS="$JAVA_OPTS -Xms8g"
JAVA_OPTS="$JAVA_OPTS -Xmn2g"
JAVA_OPTS="$JAVA_OPTS -XX:MaxDirectMemorySize=2G"
</verbatim>

			       *SDK version:*

   * IBM WebSphere SDK for Java Technology Edition Version 8.0.5.25 


                               *OS Configuration:*

				System wide resources for the app server process owner: 
   * max user processes = 65536
   * open files = 65536

			</td>
		</tr>
		<tr>
			<td>DB2</td>
			<td>ESE 10.5.0.9</td>
			<td>See [[#DBServTuning][Appendix E:  Database Server Tuning]]</td>
		</tr>
		<tr>
			<td>LDAP server</td>
			<td>N/A</td>
			<td>N/A</td>
		</tr>
		<tr>
			<td>License server</td>
			<td>N/A</td>
			<td>N/A</td>
		</tr>
		<tr>
			<td>RPT workbench</td>
			<td>9.0.0.2</td>
			<td>Defaults</td>
		</tr>
		<tr>
			<td>RPT agents</td>
			<td>9.0.0.2</td>
			<td>Defaults</td>
		</tr>
		<tr>
			<td>Network</td>
			<td> </td>
			<td>Shared subnet within test lab</td>
		</tr>
	</tbody>
</table>


--------------------
---++++!! About the author(s): 
Main.SentellaCystrunk is a performance engineer focusing on the performance and scalability of products in the Enterprise Lifecycle Management family.

--------------------
---+++++!! 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>
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.