(r9) CLMETLPerformanceReport50 < Deployment

~~EditAttach~~Printable
r9 - 2014-05-06 - 08:52:10 - Main.wangppYou are here: TWiki >
Deployment Web > DeploymentPlanningAndDesign > PerformanceDatasheetsAndSizingGuidelines > CLMETLPerformanceReport50
<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/uc.png" alt="uc.png" width="50" height="50" align="right">Collaborative Lifecycle Management performance report: Export Transform Load (ETL) 5.0 release</br>
%DKGRAY% Authors: [[Main.PengPengWang][Peng Peng Wang]]</br>
Last updated: May 5th, 2014</br>
Build basis: CLM 5.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 article presents the results of our "Extract, Transform, and Load" (ETL) performance testing for the Rational solution for Collaborative Lifecycle Managment (CLM) 5.0 release. The ETL type includes Java ETL and DM ETL. Data load includes full load and delta load. In this article, we focus on ETL performance comparison between the 5.0 release and the 4.0.6 release. 

---+++!! Disclaimer

%INCLUDE{"PerformanceDatasheetDisclaimer"}%

---++ Findings
---+++ Performance goals

   * Verify that there are no performance regressions between current release and prior release.

---+++ Findings

   * DM and JAVA ETL has similar ETL throughput for the comparison of 5.0 and 4.0.6.

   * RM part of DM and JAVA ETL has about 8% improvement due to the performance optimization of RM publish service.

---++ Topology

The topology under test is based on [[https://jazz.net/wiki/bin/view/Deployment/RecommendedCLMDeploymentTopologies#CLM_E1_Enterprise_Distributed_Li][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 are listed in *[[#AppendixA][Appendix A]]*

This report used the same test environment and same test data to test the ETL performance for CLM 4.0.* and 5.0. Test data was generated using automation. The test environment for the latest release was upgraded from the earlier one by using the CLM upgrade process. To create four VMs, one X3550 M3 (at 2.67 GHz, 48 GB RAM, and 12 physical cores) was used. In the topology, four CLM applications (JTS, CCM, QM, and RM) were installed on VM1; the CLM repository was installed on VM2; the Data Manager ETL tool was installed on VM3; and the data warehouse was installed on VM4.

The same software configuration was used for both CLM 5.0 and CLM 4.0.6. The !WebSphere Application Server was version 8.5.1, 64-bit. The database server was IBM DB2 10.1, 64-bit. The Rational Reporting for Development Intelligence tool was version 5.0. The Jazz Team Sever, CCM, QM, and RM applications co-existed in the same !WebSphere Application Server profile. The JVM was set to use an 8 GB heap with a 1 GB nursery. Server tuning details listed in *[[#AppendixA][Appendix A]]*

IBM Tivoli Directory Server was used for managing user authentication.

<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>ESXServer1</td>
			<td>1</td>
			<td>IBM X3550 M3 7944J2A </td>
			<td>1 x Intel Xeon E5-2640 2.5 GHz (six-core)</td>
			<td>12 vCPU</td>
			<td>36GB</td>
			<td>RAID0 SAS x3 300G 10k rpm </td>
			<td>900G</td>
			<td>Gigabit Ethernet</td>
			<td>ESXi4.1 </td>
		</tr>
		<tr>
			<td>JTS/RM Server</td>
			<td>1</td>
			<td>VM on IBM System x3550 M3</td>
			<td>ESX Server 1</td>
			<td>4 vCPU</td>
			<td>16GB</td>
			<td> </td>
			<td>120G</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server release 6.2 </td>
		</tr>
		<tr>
			<td>Database Server</td>
			<td>1</td>
			<td>VM on IBM System x3550 M3</td>
			<td>ESX Server 1</td>
			<td>4 vCPU</td>
			<td>16GB</td>
			<td> </td>
			<td>120G</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server release 6.2 </td>
		</tr>
			<tr>
			<td>RRDI Development Tool</td>
			<td>1</td>
			<td>VM on IBM System x3550 M3</td>
			<td>ESX Server 1</td>
			<td>2 vCPU</td>
			<td>4GB</td>
			<td></td>
			<td>120G</td>
			<td>Gigabit Ethernet</td>
			<td>Windwos 2008 Enterprise R2</td>
		</tr>
			<tr>
			<td>ESX Server2</td>
			<td>1</td>
			<td>IBM X3550 M3 7944J2A </td>
			<td>1 x Intel Xeon E5-2640 2.5GHz (six-core)</td>
			<td>12 vCPU</td>
			<td>36GB</td>
			<td>RAID0 SAS x3 300G 10k rpm </td>
			<td>900G</td>
			<td>Gigabit Ethernet</td>
			<td>ESXi4.1 </td>
		</tr>
		<tr>
			<td>CCM Server</td>
			<td>1</td>
			<td>VM on IBM System x3550 M3</td>
			<td>ESX Server 2</td>
			<td>4 vCPU</td>
			<td>16GB</td>
			<td> </td>
			<td>120G</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server release 6.2 </td>
		</tr>
		<tr>
			<td>QM Server</td>
			<td>1</td>
			<td>VM on IBM System x3550 M3</td>
			<td>ESX Server 2</td>
			<td>4 vCPU</td>
			<td>16GB</td>
			<td> </td>
			<td>120G</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server release 6.2 </td>
		</tr>
		<tr>
			<td>Data Warehouse Server</td>
			<td>1</td>
			<td>VM on IBM System x3550 M3</td>
			<td>ESX Server 1</td>
			<td>4 vCPU</td>
			<td>16GB</td>
			<td> </td>
			<td>120G</td>
			<td>Gigabit Ethernet</td>
			<td>Red Hat Enterprise Linux Server release 6.2 </td>
		</tr>		
	</tbody>
</table>

---+++Data volume and shape

The data volume listed in *[[#AppendixB][Appendix B]]*

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

---++Methodology
The ETL loads the same test data set for the different releases test on the same test environment. The test data is migrated from older release by the CLM migration. That can help to make sure the performance data is comparable among releases. The test will do the initial load to data warehouse. And then do the delta ETL load against about 10% incremental data based on initial data set.

---++Results
---+++ DM ETL Full Load
In the figure below, the performance of the DM ETL has similar performance, except RM ETL part. During CLM 5.0, the RM publish service has been optimized in order to improve the performance.  We can see there is about 8% performance improvement against RM ETL.

     <img src="%ATTACHURLPATH%/DMETLFullPerfComparison50VS406.png" alt="DMETLFullPerfComparison50VS406.png" width="785" height="456" />

---+++ DM ETL Delta Load

      <img src="%ATTACHURLPATH%/DMETLDeltaPerfComparison50VS406.png" alt="DMETLDeltaPerfComparison50VS406.png" width="780" height="336" />

NOTE: Star job does the same calculation based on all the operational data in the data warehouse. The performance of delta Star job is very similar with full Star job.  So, we only use the full ETL load to evaluate the performance of Star job.

---+++ JAVA ETL Full Load

   * Precondition: CCM ETL has one build named as Workitembaseline which records the latest info of each workitem by getting the latest workitem history record. When the workitembaseline ETL build is running, the ETL gets the latest info (status, state, priority, severity, etc.) by requesting the latest WI history with the query condition that the change time of the WI history is earlier than the ETL build start time. If there is no ETL schedule one day, the latest info of each workitem on that day are not loaded in the worktiembaseline table of DW. JAVA ETL will fill the WI latest info on the days that have no ETL running. For example, if there is no JAVA ETL run on Jan 1st, the WorkitemBaseline  table won't have chance to load the workitem latest info into DW. However, the next JAVA ETL run on Jan 2nd will insert the missing data on Jan 1st. The performance team always uses the same data set to do the ETL performance so that the performance results are comparable. This feature will cause the ETL get more workitembaseline data for the JAVA Full ETL load along with time passed. That means the baseline data of 4.0.6 is slightly more than that in 4.0.5, and that the data of 4.0.5 is slightly more than that in 4.0.4, etc. To improve the comparability of performance data release by release, we insert one pseudo record so that the ETL only inserts a single day's baseline. We get the same number of workitembaseline ELT builds inserted by this way.

In the figure below, the performance of the JAVA ETL has similar performance, except RM ETL part. During CLM 5.0, the RM publish service has been optimized in order to improve the performance.  We can see there is about 8% performance improvement against RM ETL.


     <img src="%ATTACHURLPATH%/JavaETLFullPerfComparison50VS406.png" alt="JavaETLFullPerfComparison50VS406.png" width="782" height="354" />

---+++ JAVA ETL Delta Load

   * Precondition: CCM ETL has one build named as Workitembaseline which records the latest info of each workitem by getting the latest workitem history record. When the workitembaseline ETL build is running, the ETL gets the latest info (status, state, priority, severity, etc.) by requesting the latest WI history with the query condition that the change time of the WI history is earlier than the ETL build start time. If there is no ETL schedule one day, the latest info of each workitem on that day are not loaded in the worktiembaseline table of DW. JAVA ETL will fill the WI latest info on the days that have no ETL running. For example, if there is no JAVA ETL run on Jan 1st, the WorkitemBaseline  table won't have chance to load the workitem latest info into DW. However, the next JAVA ETL run on Jan 2nd will insert the missing data on Jan 1st. The performance team always uses the same data set to do the ETL performance so that the performance results are comparable. This feature will cause the ETL get more workitembaseline data for the JAVA Full ETL load along with time passed. That means the baseline data of 4.0.6 is slightly more than that in 4.0.5, and that the data of 4.0.5 is slightly more than that in 4.0.4, etc. To improve the comparability of performance data release by release, we insert one pseudo record so that the ETL only inserts a single day's baseline. We get the same number of workitembaseline ELT builds inserted by this way.

     <img src="%ATTACHURLPATH%/JavaETLDeltaPerfComparison50VS406.png" alt="JavaETLDeltaPerfComparison50VS406.png" width="781" height="337" />

NOTE: Star job does the same calculation based on all the operational data in the data warehouse. The performance of delta Star job is very similar with full Star job.  So, we only use the full ETL load to evaluate the performance of Star job.

---++ 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 !WebSphere Application Server</td>
			<td style="vertical-align: top;">8.5.0.1</td>
			<td style="vertical-align: top;"><strong>JVM settings:</strong>

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

				<verbatim>
-verbose:gc -XX:+PrintGCDetails -Xverbosegclog:gc.log -Xgcpolicy:gencon 
-Xmx8g -Xms8g -Xmn1g -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000
-XX:MaxDirectMemorySize=1g
</verbatim>

		</td>
		</tr>
		<tr>
			<td>DB2</td>
			<td>DB2 10.1.1</td> 
<td style="vertical-align: top;"><strong>Transaction log setting of data warehouse:</strong>

    * Transaction log size changed to 40960 
<verbatim>
    db2 update db cfg using LOGFILSIZ=40960
</verbatim>

</td>

		</tr>
		<tr>
			<td>LDAP server</td>
			<td>IBM Tivoli Directory Server 6.3</td>
			<td> </td>
		</tr>
		<tr>
			<td>License server</td>
			<td> </td>
			<td>Hosted locally by JTS server</td>
		</tr>
		<tr>
			<td>Network</td>
			<td> </td>
			<td>Shared subnet within test lab</td>
		</tr>
	</tbody>
</table>
---++Appendix B
#AppendixB
<table class="gray-table">
 <tr>
  <th></th>
  <th><strong>Record type</strong></th>
  <th><strong>Initial load</strong></th>
  <th><strong>Delta load</strong></th>
 </tr>
 <tr>
  <td><strong>CCM</strong></td>
  <td>APT_ProjectCapacity</td>
  <td>1</td>
  <td>1</td>
 </tr>
 <tr>
  <td> </td>
  <td>APT_TeamCapacity</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td>Build</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td>Build Result</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td>Build Unit Test Result</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Build Unit Test Events</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Complex !CustomAttribute</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td>Custom Attribute</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>File Classification</td>
  <td>3</td>
  <td>3</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>First Stream Classification</td>
  <td>3</td>
  <td>3</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>History Custom Attribute</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>SCM Component</td>
  <td>2</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>SCM !WorkSpace</td>
  <td>2</td>
  <td>1</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem</td>
  <td>100026</td>
  <td>10000</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Approval</td>
  <td>100000</td>
  <td>10000</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Approval Description</td>
  <td>100000</td>
  <td>10000</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension</td>
  <td>3</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Approval Type</td>
  <td>3</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Category</td>
  <td>2</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Deliverable</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Enumeration</td>
  <td>34</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Resolution</td>
  <td>18</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td>Dimension</td>
  <td>68</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Dimension Type</td>
  <td>8</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Hierarchy</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td></td>
  <td> !WorkItem History</td>
  <td>242926</td>
  <td>20100</td>
 </tr>
 <tr>
   <td> </td>
   <td> !WorkItem History Complex Custom Attribute</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td> </td>
  <td> !WorkItem Link</td>
  <td>112000</td>
  <td>10000</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td> !WorkItem Type Mapping</td>
  <td>4</td>
  <td>0</td>
 </tr>
 <tr>
  <td><strong>RM</strong></td>
  <td> !CrossAppLink</td>
  <td>605658</td>
  <td>88293</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Custom Attribute</td>
  <td>422710</td>
  <td>51073</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Requirement</td>
  <td>424760</td>
  <td>51393</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Collection Requirement Lookup</td>
  <td>163110</td>
  <td>37200</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Module Requirement Lookup</td>
  <td>206000</td>
  <td>20000</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Implemented BY</td>
  <td>100</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Request Affected</td>
  <td>5988</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Request Tracking</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>REQUICOL_TESTPLAN_LOOKUP</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>REQUIREMENT_TESTCASE_LOOKUP</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
 <tr>
  <td>&nbsp;</td>
  <td>REQUIREMENT_SCRIPTSTEP_LOOKUP</td>
  <td>24000</td>
  <td>2400</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>REQUIREMENT_HIERARCHY</td>
  <td>12626</td>
  <td>2328</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>REQUIREMENT_EXTERNAL_LINK</td>
  <td>0</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td> !RequirementsHierarchyParent</td>
  <td>6184</td>
  <td>0</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Attribute Define</td>
  <td>10</td>
  <td>10</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Requirement Link Type</td>
  <td>176</td>
  <td>176</td>
 </tr>
 <tr>
  <td>&nbsp;</td>
  <td>Requirement Type</td>
  <td>203</td>
  <td>203</td>
 </tr>
</table>
<table class="gray-table">
 <tr>
  <th><strong>QM</strong></th>
  <th><strong>Record type</strong></th>
  <th></th>
  <th><strong>Initial load</strong></th>
  <th><strong>Delta load</strong></th>
 </tr>
<tr> <td></td>  <td>TestScript</td> <td></td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>BuildRecord</td> <td></td> <td>2000</td> <td>200</td> </tr>
<tr> <td></td>  <td>Category</td> <td></td> <td>55</td> <td>12</td> </tr>
<tr> <td></td>  <td>CategoryType</td> <td></td> <td>12</td> <td>0</td> </tr>
<tr> <td></td>  <td>Current log of Test Suite </td> <td></td> <td>600</td> <td>60</td> </tr>
<tr> <td></td>  <td>EWICustomAttribute</td> <td></td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>EWIRelaLookup</td> <td></td> <td></td> <td></td> </tr>
<tr> <td></td>  <td></td><td>CONFIG_EXECUTIONWORKITM_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>EXECWORKITEM_REQUEST_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>EXECWORKITEM_ITERATION_LOOKUP</td> <td>18000</td> <td>1800</td> </tr>
<tr> <td></td>  <td></td><td>EXECWORKITEM_CATEGORY_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>ExecResRelaLookup</td> <td></td> <td></td> <td></td> </tr>
<tr> <td></td>  <td></td><td>EXECRES_EXECWKITEM_LOOKUP</td> <td>54000</td> <td>5400</td> </tr>
<tr> <td></td>  <td></td><td>EXECRES_REQUEST_LOOKUP</td> <td>6001</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>EXECRESULT_CATEGORY_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>EXECUTION_STEP_RESULT</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>ExecStepResRequestLookup</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>ExecutionResult</td> <td></td><td>54000</td> <td>5400</td> </tr>
<tr> <td></td>  <td>ExecutionStepResult</td><td></td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>ExecutionWorkItem</td><td></td> <td>18000</td> <td>1800</td> </tr>
<tr> <td></td>  <td>Job</td><td></td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>JobResult</td><td></td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>KeyWord</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>KeyWordTestScriptLookup</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>LabRequestChangeState</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>LabRequest</td><td></td> <td>252</td> <td>25</td> </tr>
<tr> <td></td>  <td>LabResource</td> <td></td><td>2400</td> <td>2640</td> </tr>
<tr> <td></td>  <td>Objective</td><td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>Priority</td> <td></td><td>4</td> <td>0</td> </tr>
<tr> <td></td>  <td>RemoteScript</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>Requirement</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>Reservation</td> <td></td><td>3199</td> <td>320</td> </tr>
<tr> <td></td>  <td>ReservationRequestLookup</td> <td></td><td>3</td> <td>12</td> </tr>
<tr> <td></td>  <td>ResourceGroup</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>ScriptStep_Rela_Lookup</td> <td></td><td>24000</td> <td>2397</td> </tr>
<tr> <td></td>  <td>State</td> <td></td><td>24</td> <td>0</td> </tr>
<tr> <td></td>  <td>StateGroup</td> <td></td><td>6</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestCase</td> <td></td><td>6000</td> <td>600</td> </tr>
<tr> <td></td>  <td>TestCaseCustomAttribute</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestCaseRelaLookup</td> <td></td><td></td> <td></td> </tr> 
<tr> <td></td>  <td></td><td>TESTCASE_RemoteTESTSCRIPT_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TESTCASE_TESTSCRIPT_LOOKUP</td> <td>6000</td> <td>600</td> </tr>
<tr> <td></td>  <td></td><td>TESTCASE_CATEGORY_LOOKUP</td> <td>16106</td> <td>1598</td> </tr>
<tr> <td></td>  <td></td><td>REQUIREMENT_TESTCASE_LOOKUP</td> <td>6000</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>REQUEST_TESTCASE_LOOKUP</td> <td>6000</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TestCase !RelatedRequest Lookup</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestEnvironment</td> <td></td> <td>400</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestPhase</td> <td></td><td>120</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestPlan</td> <td></td><td>11</td> <td>1</td> </tr>
<tr> <td></td>  <td>TestPlanObjectiveStatus</td><td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestPlanRelaLookup</td> </td><td></td><td></td> <td></td> </tr>
<tr> <td></td>  <td></td><td>REQUIREMENT_TESTPLAN_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TESTSUITE_TESTPLAN_LOOKUP</td> <td>600</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TESTPLAN_CATEGORY_LOOKUP</td> <td>0</td> <td>2</td> </tr>
<tr> <td></td>  <td></td><td>TESTPLAN_TESTCASE_LOOKUP</td> <td>6000</td> <td>600</td> </tr>
<tr> <td></td>  <td></td><td>TESTPLAN_OBJECTIVE_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>REQUIREMENT COLLECTION_TESTPLAN_LOOKUP</td> <td>32</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TESTPLAN_TESTPLAN_HIERARCHY</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TESTPLAN_ITERATION_LOOKUP</td> <td>120</td> <td>12</td> </tr>
<tr> <td></td>  <td></td><td>REQUEST_TESTPLAN_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestScript</td> <td></td><td>6000</td> <td>1200</td> </tr>
<tr> <td></td>  <td>TestScriptRelaLookup _ Manual</td>  <td></td><td></td> <td></td> </tr>
<tr> <td></td>  <td></td><td>TESTSCRIPT_CATEGORY_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>REQUEST_TESTSCRIPT_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestScriptRelaLookup _ Remote</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestScriptStep</td> <td></td><td>24000</td> <td>2397</td> </tr>
<tr> <td></td>  <td>TestSuite</td> <td></td><td>600</td> <td>60</td> </tr>
<tr> <td></td>  <td>TestSuite_CusAtt</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestSuiteElement</td> <td></td><td>9000</td> <td>900</td> </tr>
<tr> <td></td>  <td>TestSuiteExecutionRecord</td> <td></td><td>600</td> <td>60</td> </tr>
<tr> <td></td>  <td>TestSuiteLog</td> <td></td><td>3000</td> <td>300</td> </tr>
<tr> <td></td>  <td>TestSuiteRelaLookup</td><td></td><td></td> <td></td> </tr>
<tr> <td></td>  <td></td><td>TESTSUITE_CATEGORY_LOOKUP</td> <td>1595</td> <td>155</td> </tr>
<tr> <td></td>  <td></td><td>REQUEST_TESTSUITE_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestSuLogRelaLookup</td> <td></td><td></td> <td></td> </tr>
<tr> <td></td>  <td></td><td>TESTSUITE_TESTSUITELOG_LOOKUP</td> <td>3000</td> <td>300</td> </tr>
<tr> <td></td>  <td></td><td>TESTSUITELOG_EXECRESULT_LOOKUP</td> <td>21303</td> <td>2106</td> </tr>
<tr> <td></td>  <td></td><td>TESTSUITELOG_CATEGORY_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>TestSuiteExecutionRecord_CusAtt</td> <td></td><td>600</td> <td>60</td> </tr>
<tr> <td></td>  <td>TSERRelaLookup</td> <td></td><td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td></td><td>TSTSUITEXECREC_CATEGORY_LOOKUP</td> <td>0</td> <td>0</td> </tr>
<tr> <td></td>  <td>Total</td> <td></td><td>299682</td> <td>31094</td> </tr>
</table>

N/A: Not applicable.


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

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

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

Main.PengPengWang

--------------------
---+++++!! 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>
Attachments
Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
png	DMETLDeltaPerfComparison50VS406.png	manage	8.5 K	2014-05-05 - 04:05	UnknownUser	DMETLDeltaPerfCOmparison50VS406
png	DMETLFullPerfComparison50VS406.png	manage	12.0 K	2014-05-05 - 04:04	UnknownUser	DMETLFullPerfCOmparison50VS406
png	JavaETLDeltaPerfComparison50VS406.png	manage	7.6 K	2014-05-05 - 05:29	UnknownUser	JavaETLDeltaPerfComparison50VS406
png	JavaETLFullPerfComparison50VS406.png	manage	7.8 K	2014-05-05 - 05:28	UnknownUser	JavaETLFullPerfComparison50VS406
Deployment
Community information and contribution guidelines
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
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.