ReliabilityTestingOfCLM406 < Deployment

<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.TWikiAdminGroup, Main.TWikiDeploymentDatasheetsAuthorsGroup, Main.GrantCovell
-->
---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right">CLM Reliability report: CLM 4.0.6 release</br>
%DKGRAY% Authors: Main.MarkGravina</br>
Last updated: Feb. 3, 2014</br>
Build basis: Collaborative Lifecycle Management 4.0.6
%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

Reliability testing is about exercising the CLM applications so that failures are discovered and removed before the system is deployed.  There are many different combinations of alternate pathways through the complex CLM application, this test scenario exercises the most likely use cases (explained in detail below). The use cases are put under constant load for a seven day period to validate that the CLM application provides the expected level of service, without any downtime or degradation in overall system performance. This report is a sample of the results from a CLM 4.0.6 RC2 Reliability test.  

---+++!! Disclaimer

%INCLUDE{"PerformanceDatasheetDisclaimer"}%

---++ Findings

---+++ Performance goals
---++++Primary Goals - Detection

   * Test the CLM software performance under given conditions, and monitoring for any degradation in performance over the course of the 7 day run.
   * Monitor for increases in the overall page or page element averages.
   * Report on any specific page which increases over time.
---++++Secondary Goals - Analysis

   * To discover the main cause of any failure.
   * To find and correlate the structure of repeating failures.
---+++ Findings

   * Completion of 7 day run without any crashes or noticeable degradation in performance.
   * Several page transactions were visibly increasing in response time over the seven day period.  Further analysis of these specific transaction will be conducted.   
   * Final load results will be further analyzed to determine if the actual load fits within our anticipated scalability needs.
   * With the addition of floating license hosting and usage, there was no impact on the reliability of the system.
   

---++ Topology

The topology under test is based on [[https://jazz.net/library/article/820#Enterprise_Distributed_Linux__DB2][Standard Topology (E1) Enterprise - Distributed / Linux / DB2.]]

<img src="https://jazz.net/library/content/articles/clm/2011/standard-clm-topologies/images/Enterprise_Distributed_Linux_DB2_640.png" alt="Server Overview" width="70%" height="70%" />

The specifications of machines under test are listed in the table below. Server tuning details listed in *[[#AppendixA][Appendix A]]*

<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 Cores/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>IBM HTTP Server and !WebSphere Plugin</td>
			<td>1</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v8GB</td>
			<td>VMFS</td>
			<td>v30GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, !WebSphere Application Server 8.5.5.0 64-bit</td>
		</tr>
		<tr>
			<td>JTS Server</td>
			<td>1</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v16GB</td>
			<td>VMFS</td>
			<td>V100GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, 	!WebSphere Application Server 8.5.5.0 64-bit</td>
		</tr>
		<tr>
			<td>CCM Server</td>
			<td>1</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v8GB</td>
			<td>VMFS</td>
			<td>v50GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64,	!WebSphere Application Server 8.5.5.0 64-bit</td>
		</tr>
		<tr>
			<td>QM Server</td>
			<td>1</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v8GB</td>
			<td>VMFS</td>
			<td>v50GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, !WebSphere Application Server 8.5.5.0 64-bit</td>
		</tr>
		<tr>
			<td>RM Server</td>
                       	<td>1</td>		
                        <td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v8GB</td>
			<td>VMFS</td>
			<td>v50GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, 	!WebSphere Application Server 8.5.5.0 64-bit</td>
		</tr>
                <tr>
			<td>DB2 Server</td>
			<td>1</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v16GB</td>
			<td>VMFS</td>
			<td>V100GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, 	DB2 Enterprise 10.1.0.2</td>
		</tr>		
                 <tr>
			<td>LDAP Server</td>
			<td>1</td>
			<td>ThinkCentre M57p</td>
			<td>1 x Intel Core 2 Duo E6750 2.66GHz (dual-core)</td>
			<td>2</td>
			<td>2GB</td>
			<td>SATA Disk</td>
			<td>250GB</td>
			<td>Gigabit Ethernet</td>
			<td>Windows 2003 Enterprise, Tivoli Directory Server 6.1</td>
		</tr>		                 
<tr>
			<td>RPT Workbench</td>
			<td>1</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v16GB</td>
			<td>VMFS</td>
			<td>v100GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, 	Rational Performance Tester 8.3.0.3 64-bit</td>
		</tr>
		<tr>
			<td>RPT Agent</td>
			<td>6</td>
			<td>VMWare Image</td>
			<td>VMWare Hypervisor, Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz</td>
			<td>v4</td>
			<td>v8GB</td>
			<td>VMFS</td>
			<td>v100GB</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Linux Server 2.6.32-358.6.1.el6.x86_64, 	Rational Performance Tester Agent 8.3.0.3 64-bit</td>
		</tr>
	</tbody>
</table>


---+++Network connectivity

All CLM server machines and RPT test driver machines are located on the same subnet. The LAN has 1000 Mbps of maximum bandwidth, and the average latency between the IHS server and all distributed Application Servers is 1.12ms.  
The LDAP Server is also on the same subnet, but has a latency of less than 0.8ms with the CLM Servers.

---+++Data volume and shape

At the beginning of the test the repository projects were populated to have the following size:

   * RM/DNG - 10 projects with 100K artifacts
   * CCM - 10 projects populated with 100K artifacts
   * QM - 10 projects populated with 100K artifacts
   * Admin – 10 CLM projects with artifacts linked across all projects



---++Methodology

Rational Performance Tester was used to simulate the CLM workload created using the
web client. Each user is distributed across a set of user groups.  Each user group 
represents a CLM product area, e.g. CCM, QM, RM. Each user group performs a random 
set of use cases 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 single user action.

Based on real customer use, the CLM test scenario provides a ratio of 70% reads
and 30% writes. The users completed use cases at a rate of 6.25 pages per
second, over a seven day period. Each CLM performance test runs for seven days
with no decline in usage or other downtime. 

RPT Schedule Element Details:
   * Number of users: 400
   * Stage: One stage, 7 days
   * Rate: One user every 10 seconds
   * Settle Time: 90 minutes
   * Think Time: 60000ms, varied by random %, Lower limit 50%, Upper limit 150%

CLM group schedule distribution:
   * CCM 45%
   * RQM 30%
   * Integrations 10%
   * RM 10%
   * DNG Web Client 5%

Test cases with the higher weights will be run more frequently within the User Groups.  


---+++CLM test cases and weighted distribution
#TestCases
<table class="gray-table">
	<tbody>
		<tr>
			<th align="center">Use case</th>
			<th align="center">Description</th>
                        <th align="center">User Group</th>
			<th align="center">Weight within User Group loop</th>
		</tr>
		<tr>
			<td>RTC_CreateDefect</td>
			<td>CCM User logs in to their project dashboard, creates a defect, then logs out.</td>
                        <td>CCM</th>
			<td align="center">5</td>
		</tr>
		<tr>
			<td>RTC_QueryAndEditDefect</td>
                        <td>CCM User logs in to their project dashboard, queries for a defect, edits defect, then logs out.</td>
			<td>CCM</td>
			<td align="center">10</td>
		</tr>
		<tr>
			<td>RTC_QueryAndViewDefect</td>
                        <td>CCM User logs in to their project dashboard, queries for a defect, views defect, then logs out.</td>
			<td>CCM</td>
			<td align="center">60</td>
		</tr>
		<tr>
			<td>QM_CreateTestCase</td>
                        <td>QM User logs in to their project dashboard and creates a test case.</td>
			<td>QM</td>
			<td align="center">6</td>
		</tr>
		<tr>
			<td>QM_CreateTestPlan</td>
                        <td>QM User logs in to their project dashboard and creates a test plan.</td>
			<td>QM</td>
			<td align="center">2</td>
		</tr>
		<tr>
			<td>QM_BrowseTERs</td>
                        <td>QM User logs in to their project dashboard, then browses Test Case Execution Records.</td>
			<td>QM</td>
			<td align="center">10</td>
		</tr>
		<tr>
			<td>QM_editTestScript</td>
                        <td>QM User logs in to their project dashboard, opens and edits a test script.</td>
			<td>QM</td>
			<td align="center">18</td>
		</tr>
		<tr>
			<td>QM_editTestPlan</td>
                        <td>QM User logs in to their project dashboard, opens and edits a test plan.</td>
			<td>QM</td>
			<td align="center">5</td>
		</tr>
		<tr>
			<td>QM_editTestCase</td>
                        <td>QM User logs in to their project dashboard, opens and edits a test case.</td>
			<td>QM</td>
			<td align="center">18</td>
		</tr>
		<tr>
			<td>QM_createTestScript</td>
                        <td>QM User logs in to their project dashboard and creates a test script.</td>
			<td>QM</td>
			<td align="center">6</td>
		</tr>
		<tr>
			<td>QM_executeTestSteps4</td>
                        <td>QM User logs in to their project dashboard, searches for TER, executes a 4 step TER then shows results.</td>
			<td>QM</td>
			<td align="center">60</td>
		</tr>
		<tr>
			<td>QPlan to Req Collection</td>
                        <td>RQM User logs in, creates a new test plan, and then creates a new quality task and links it to an RTC task, then logs out.</td>
			<td>Int</td>
			<td align="center">1</td>
		</tr>
		<tr>
			<td>TestPlanLinks</td>
                        <td>QM User logs in, creates a new test plan, and then links the test plan to a RTC Plan, then logs out.</td>
			<td>Int</td>
			<td align="center">1</td>
		</tr>
		<tr>
			<td>Test case links Dev item</td>
                        <td>QM User logs in, creates a new test case and links it to an RTC workitem, then logs out.</td>
			<td>Int</td>
			<td align="center">5</td>
		</tr>
		<tr>
			<td>TER Links</td>
                        <td>QM User logs in to their project, creates and runs a new test case, then creates a linked RTC defect to the TER, user logs out.</td>
			<td>Int</td>
			<td align="center">5</td>
		</tr>
		<tr>
			<td>Test script Links</td>
                        <td>QM User logs in to their project, creates a new test script and links it to an RTC workitem, then logs out.</td>
			<td>Int</td>
			<td align="center">5</td>
		</tr>
		<tr>
			<td>Show RM Traceability viewlet</td>
                        <td>QM User logs in to their project dashboard and adds a remote RM traceability viewlet. Save Dashboard, user logs out.</td>
			<td>Int</td>
			<td align="center">1</td>
		</tr>
		<tr>
			<td>Test Case links</td>
                        <td>QM User logs in to their project, creates a new test case and links it to an RM requirement artifact. User logs out.</td>
			<td>Int</td>
			<td align="center">1</td>
		</tr>
		<tr>
			<td>SaveModule</td>
                        <td>DNG Web user logs in, opens, edits, and saves a large module.</td>
			<td>DNG Web</td>
			<td align="center">3</td>
		</tr>
                 <tr>
			<td>SwitchModule</td>
                        <td>DNG Web user logs in, opens a random module, then switches view and opens another module.</td>
			<td>DNG Web</td>
			<td align="center">6</td>
		</tr>
                <tr>
			<td>AddModuleComment</td>
                        <td>DNG Web user opens a large module inserts a comment, saves module.</td>
			<td>DNG Web</td>
			<td align="center">8</td>
		</tr>
                <tr>
			<td>OpenLargeModule</td>
                        <td>DNG Web user logs in and opens a large module.</td>
			<td>DNG Web</td>
			<td align="center">8</td>
		</tr>
                <tr>
			<td>DisplayModuleHistory</td>
                        <td>DNG Web user logs in to their project, opens a module then selects display module history.</td>
			<td>DNG Web</td>
			<td align="center">4</td>
		</tr>
                <tr>
			<td>CreateArtifactLargeModule</td>
                        <td>DNG User logs in to their project, edits a large module by adding an artifact to it.  Save module.</td>
			<td>DNG Web</td>
			<td align="center">4</td>
		</tr>
                <tr>
			<td>OpenAndScrollLargeModule</td>
                        <td>DNG Web User logs in, opens a large module, then scrolls through the entire 1000 artifacts.</td>
			<td>DNG Web</td>
			<td align="center">8</td>
		</tr>
                <tr>
			<td>ReviewLargeModule</td>
                        <td>DNG Web user logs in, opens a large module, creates and executes a review cycle on the module.</td>
			<td>DNG Web</td>
			<td align="center">1</td>
		</tr>
                <tr>
			<td>EditModuleArtifact</td>
                        <td>DNG Web user logs in, opens a large module, edits the title of one of the artifacts in the module, saves edits, saves module.</td>
			<td>DNG Web</td>
			<td align="center">4</td>
		</tr>
                <tr>
			<td>ManageFolders</td>
                        <td>RM User logs in, creates a folder, move it to a new location, and then delete the folder.</td>
			<td>RM</td>
			<td align="center">7</td>
		</tr>
                <tr>
			<td>ViewCollections</td>
                        <td>RM User logs in to their project then views collections that contain 100 artifacts from the collections folders.</td>
			<td>RM</td>
			<td align="center">12</td>
		</tr>
                <tr>
			<td>CreateLinks</td>
                        <td>RM user logs in to their project, opens an artifact and creates a link to another RM artifact.</td>
			<td>RM</td>
			<td align="center">10</td>
		</tr>
                <tr>
			<td>CreateOSLC link</td>
                        <td>RM User logs in to their project, creates a new artifact and links it as validated by the creation of a new QM Test Case.</td>
			<td>RM</td>
			<td align="center">6</td>
		</tr>
                <tr>
			<td>NestedLoop</td>
                        <td>RM User logs in to their project and then opens three levels of nested folders.</td>
			<td>RM</td>
			<td align="center">7</td>
		</tr>
                <tr>
			<td>FilterQuery</td>
                        <td>RM User logs in to their project dasboard then runs a filtered query.</td>
			<td>RM</td>
			<td align="center">6</td>
		</tr>
                <tr>
			<td>QuerybyID</td>
                        <td>RM User logs in to their project and runs a query by id.</td>
			<td>RM</td>
			<td align="center">4</td>
		</tr>
                <tr>
			<td>QuerybyString</td>
                        <td>RM User logs in to their project, then runs a query by specifying a string.</td>
			<td>RM</td>
			<td align="center">8</td>
		</tr>
                <tr>
			<td>HoverCollection</td>
                        <td>RM User logs in to their project, opens the collection folder, then hovers over one of the collections until the rich hover appears.</td>
			<td>RM</td>
			<td align="center">6</td>
		</tr>
                <tr>
			<td>CreateArtifact</td>
                        <td>RM User logs in to their project, creates an artifact, edits the artifact and inserts text and images, then saves the artifact.</td>
			<td>RM</td>
			<td align="center">3</td>
		</tr>
                <tr>
			<td>CreateMultiValueArt</td>
                        <td>RM User logs in to their project, creates a multi value artifact then adds multi value attributes.</td>
			<td>RM</td>
			<td align="center">3</td>
		</tr>
           	</tbody>
</table>







---++Results

*IHS Thread Analysis*

IHS threads usage is monitored to determine how well IHS server was keeping up with the load, and determine if IHS was tuned properly to move the threads through the system most efficiently.
The following chart shows how well the IHS server was handling it's threads, and of note are the threads in WAS module which do not accumulate over time which indicates the !WebSphere Application
servers are keeping up with the load. 
IHS server-status command monitoring indicates the webserver is processing approximately 91.4 requests/sec. 

The gaps shown below mid-day5, reflect an outage of one of the RPT agent drivers, but did not impact any of the running CLM applications.

<img src="%ATTACHURLPATH%/ihsthreads.png" width="40%" height="40%"/>


*RPT Page Hit Rate*

RPT Page Hit Rate is captured to monitor the load and help with correlation of any incidences where load changes. For purposes of this test the load is constant.  

<img src="%ATTACHURLPATH%/page_hitrate.png" width="25%" height="25%"/>


*RPT Page Element Response over Time*

Page Element Response Rate is captured to monitor the average page element response over time.  


<img src="%ATTACHURLPATH%/page_element_response.png" width="25%" height="25%"/>

*RPT Average Page Response Time*

RPT Average Page Response Time shows the average of all pages over time. This is very useful in determining which if/any pages are unexpectedly increasing in response time over the seven day period. 

<img src="%ATTACHURLPATH%/avg_page_response.png" width="40%" height="40%"/>

*RPT Byte Transfer Rate*

RPT Byte Transfer Rate shows us if bytes being sent or received are changing over time, indicating a drop in throughput. 

<img src="%ATTACHURLPATH%/byte_xfer.png" width="25%" height="25%"/>


---++ Appendix A
#AppendixA
<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="600"><strong>Highlights for configurations under test</strong></th>
		</tr>
		<tr>
			<td style="vertical-align: top;">IBM HTTP Server for !WebSphere Application Server</td>
			<td style="vertical-align: top;">8.5.5.0</td>
			<td style="vertical-align: top;">IBM HTTP Server functions as a reverse proxy server implemented
via Web server plug-in for !WebSphere Application Server. Configuration details can be found from the [[http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_config_reverse_proxy_ihs.html][CLM infocenter]].

*HTTP server (httpd.conf)*:



!MaxClients: increase value for high-volume loads [[http://publib.boulder.ibm.com/httpserv/ihsdiag/ihs_performance.html][(adjust value based on user load)]]
   * !ThreadsPerChild = 50
   * !Timeout 150
   * !MaxKeepAliveRequests 100
   * !KeepAliveTimeout         8
   * !ThreadLimit                 25
   * !ServerLimit                 100
   * !StartServers               2
   * !MaxClients                  800
   * !MinSpareThreads     	  25
   * !MaxSpareThreads     	 100
   * !ThreadsPerChild          25
   * !MaxRequestsPerChild   0

*Web server plugin-in (plugin-cfg.xml)*:

   * !ServerIOTimeout="60"

*OS Configuration*:

   * max user processes = unlimited
      </td>
		</tr>
		<tr>
			<td style="vertical-align: top;">IBM !WebSphere Application Server Network Deployment for JTS, Admin, and CLMHelp applications</td>
			<td style="vertical-align: top;">8.5.5.0</td>
			<td style="vertical-align: top;"><strong>JVM settings:</strong>

   * GC policy and arguments, max and init heap sizes:

				<verbatim>
 -Xgcpolicy:gencon -Xmx8g -Xms8g -Xmn2g -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -XX:MaxDirectMemorySize=2g
</verbatim>

				*Thread pools:*

   * Maximum !WebContainer = Minimum !WebContainer = 200


				*OS Configuration:*

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

			</td>
		</tr>
<tr>
			<td style="vertical-align: top;">IBM !WebSphere Application Server Network Deployment for CCM application</td>
			<td style="vertical-align: top;">8.5.5.0</td>
			<td style="vertical-align: top;"><strong>JVM settings:</strong>

   * GC policy and arguments, max and init heap sizes:

				<verbatim>
 -Xgcpolicy:gencon -Xmx8g -Xms4g -Xmn512m -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -XX:MaxDirectMemorySize=1g
</verbatim>

				*Thread pools:*

   * Maximum !WebContainer = Minimum !WebContainer = 200


				*OS Configuration:*

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

			</td>
		</tr>		

<tr>
			<td style="vertical-align: top;">IBM !WebSphere Application Server Network Deployment QM application</td>
			<td style="vertical-align: top;">8.5.5.0</td>
			<td style="vertical-align: top;"><strong>JVM settings:</strong>

   * GC policy and arguments, max and init heap sizes:

				<verbatim>
 -Xgcpolicy:gencon -Xmx4g -Xms4g -Xmn512m -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -XX:MaxDirectMemorySize=1g
</verbatim>

				*Thread pools:*

   * Maximum !WebContainer = Minimum !WebContainer = 200


				*OS Configuration:*

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

			</td>
		</tr>

<tr>
			<td style="vertical-align: top;">IBM !WebSphere Application Server Network Deployment for RM, Converter applications</td>
			<td style="vertical-align: top;">8.5.5.0</td>
			<td style="vertical-align: top;"><strong>JVM settings:</strong>

   * GC policy and arguments, max and init heap sizes:

				<verbatim>
 -Xgcpolicy:gencon -Xmx4g -Xms4g -Xmn512m -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -XX:MaxDirectMemorySize=1g
</verbatim>

				*Thread pools:*

   * Maximum !WebContainer = Minimum !WebContainer = 200


				*OS Configuration:*

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

			</td>
		</tr>

                <tr>
			<td>DB2</td>
			<td>DB2 10.1</td>
			<td> </td>
		</tr>
		<tr>
			<td>LDAP server</td>
			<td> </td>
			<td> </td>
		</tr>
		<tr>
			<td>License server</td>
			<td> </td>
			<td>Hosted locally by JTS server</td>
		</tr>
		<tr>
			<td>RPT Workbench</td>
			<td>8.3.0.3</td>
			<td>Defaults</td>
		</tr>
		<tr>
			<td>RPT agents</td>
			<td>8.3.0.3</td>
			<td>Defaults</td>
		</tr>
		<tr>
			<td>Network</td>
			<td> </td>
			<td>Shared subnet within test lab</td>
		</tr>
	</tbody>
</table>

*Garbage collection*

Verbose garbage collection analysis helps determine how the memory and garbage collection are performing for the CLM applications running our use cases. Optimal JVM configuration depends very greatly on the usage pattern. Our goal is to provide guidance on where to start and what key tuning factors impact performance.  

The gaps shown below mid-day5, reflect an outage of one of the RPT agent drivers, but did not impact any of the running CLM applications.

*JTS*

<img src="%ATTACHURLPATH%/AppNodeJTS_gc.png" width="50%" height="50%"/>   <img src="%ATTACHURLPATH%/legend.png" width="15%" height="15%"/>

*CCM*

<img src="%ATTACHURLPATH%/AppNodeCCM_gc.PNG" width="50%" height="50%" />  <img src="%ATTACHURLPATH%/legend.png" width="15%" height="15%"/>

*QM*

<img src="%ATTACHURLPATH%/AppNodeQM_gc.png" width="50%" height="50%"/>  <img src="%ATTACHURLPATH%/legend.png" width="15%" height="15%"/>

*RM*

<img src="%ATTACHURLPATH%/AppNodeRM_gc.png" width="50%" height="50%"/>  <img src="%ATTACHURLPATH%/legend.png" width="15%" height="15%"/>

---++++!! For more information

   * [[SizingReportCLM2012][Collaborative Lifecycle Management 2012 Sizing Report (Standard Topology E1)]]

---++++!! About the authors

Main.MarkGravina

--------------------
---+++++!! 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 > WebHome > DeploymentPlanningAndDesign > PerformanceDatasheetsAndSizingGuidelines > ReliabilityTestingOfCLM406
History: r7 - 2014-02-05 - 20:06:42 - 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.