Engineering Lifecycle Management Wiki - Deployment
Deployment Web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
E
dit
A
ttach
P
rintable
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
CollaborativeLifecycleManagementPerformanceReportRQM604Release
Revision 9 - 2019-04-15 - 21:32:22 - 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 --> ---+!! Collaborative Lifecycle Management performance report: Rational Quality Manager 6.0.4 release</br> %DKGRAY% Authors: [[Main.HongyanHuo][Hongyan Huo]]</br> Last updated: May 20, 2017</br> Build basis: Rational Quality Manager 6.0.4 %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 report compares the performance of <b>Rational Quality Manager (RQM) </b> version 6.0.4 to the previous 6.0.3 release, using a large repository that contains 10 million test artifacts in total. The goal of the test was the verify that the performance of the 6.0.4 operations were the same or better than their 6.0.3 equivalents. The test methodology involves these steps: * Collect the standard one-hour performance test data using 1,000 concurrent users from RQM 6.0.3 (repeat 2 times) * Repeat the same standard one-hour performance test load against RQM 6.0.4 using 1,000 concurrent users (repeat 2 times) * Compare the 4 runs ---+++!! Disclaimer %INCLUDE{"PerformanceDatasheetDisclaimerEndToEnd"}% ---++ Summary of performance results We applied the standard performance load using a large QM repository containing 10 million artifacts against RQM 6.0.3 and 6.0.4 respectively (refer to section [[#Data_volume_and_shape][Data volume and shape]] for details). Test results showed the general performance of 6.0.4 is better than the 6.0.3 equivalents. Most of the pages under test were observed to be faster, comparing 6.0.4 to 6.0.3, which resulted in an overall 25% decrease in average page response time by all pages, as seen in the chart below. <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/AveragePageResponseTimeAllPages_604vs603.png" /> There are a certain number of significant performance improvements made into 604, including viewing a test suite containing large number of test cases, selecting test scripts to add to a test case, and viewing test schedules for a test plan. Below is a chart showing the top pages that have been improved greatly <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/perfImprovement_604M5vs603GA.png" /> For more details on the 1000 user workload, see this section: [[#User_roles_test_cases_and_worklo][User roles, test cases and workload characterization ]]. For the detailed performance results for each use case, see this section: [[#DetailedResults][Detailed performance results]]. ---+++ Summary of OS resource utilization Comparing system resource data for both 6.0.4 release and 6.0.3, 6.0.4 has * Reduced CPU utilization on both DB server WAS application server than 6.0.3 * Reduced network I/O than 6.0.3 * Slightly reduced disk utilization on both DB server WAS application server than 6.0.3 * Similar memory consumption for QM DB on the DB server with 6.0.3 The details are provided in section [[#Resource_utilization][Resource utilization]] ---++ Appendix A: Topology The topology under test is based on [[RecommendedCLMDeploymentTopologies#CLM_E1_Enterprise_Distributed_Li][Standard Topology (E1) Enterprise - Distributed / Linux / DB2.]] <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM50Release/ServerOverview.png" alt="ServerOverview.png"width="40%" height="40%" /> The specifications of machines under test are listed in the table below. Server tuning details listed in *[[#Appendix_D_Key_configuration_par][Appendix D: Key configuration parameters]]* <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>Proxy Server (IBM HTTP Server and !WebSphere Plugin)</td> <td>1</td> <td>IBM System x3250 M4</td> <td>1 x Intel Xeon E3-1240 3.4GHz (quad-core)</td> <td>8</td> <td>16GB</td> <td>RAID 1 -- SAS Disk x 2</td> <td>299GB</td> <td>Gigabit Ethernet</td> <td>Red Hat Enterprise Linux Server release 6.5</td> </tr> <tr> <td>JTS Server</td> <td>1</td> <td>IBM System x3550 M4</td> <td>2 x Intel Xeon E5-2640 2.5GHz (six-core)</td> <td>24</td> <td>32GB</td> <td>RAID 5 -- SAS Disk x 2</td> <td>897GB</td> <td>Gigabit Ethernet</td> <td>Red Hat Enterprise Linux Server release 6.5</td> </tr> <tr> <td>QM Server</td> <td>1</td> <td>IBM System x3550 M4</td> <td>2 x Intel Xeon E5-2640 2.5GHz (six-core)</td> <td>24</td> <td>32GB</td> <td>RAID 5 -- SAS Disk x 2</td> <td>897GB</td> <td>Gigabit Ethernet</td> <td>Red Hat Enterprise Linux Server release 6.5</td> </tr> <tr> <td>Database Server</td> <td>1</td> <td>IBM System x3650 M4</td> <td>2 x Intel Xeon E5-2640 2.5GHz (six-core)</td> <td>24</td> <td>64GB</td> <td>RAID 5 -- SAS Disk x 2</td> <td>2.4TB</td> <td>Gigabit Ethernet</td> <td>Red Hat Enterprise Linux Server release 6.1</td> </tr> <tr> <td>RPT workbench</td> <td>1</td> <td>IBM System x3550 M4</td> <td>2 x Intel Xeon E5-2640 2.5GHz (six-core)</td> <td>24</td> <td>32GB</td> <td>RAID 5 -- SAS Disk x 2</td> <td>897GB</td> <td>Gigabit Ethernet</td> <td>Red Hat Enterprise Linux Server release 6.4</td> </tr> <tr> <td>RPT Agents</td> <td>6</td> <td>VM image</td> <td>4 x Intel Xeon X5650 CPU (1-Core 2.67GHz)</td> <td>1</td> <td>2GB</td> <td>N/A</td> <td>30GB</td> <td>Gigabit Ethernet</td> <td>Red Hat Enterprise Linux Server release 6.5</td> </tr> <tr> <td>Network switches</td> <td>N/A</td> <td>Cisco 2960G-24TC-L</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>24 Ethernet 10/100/1000 ports</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 The artifacts were migrated from 6.0.3GA repository which contains a total of 10.7M artifacts in *one* large project. The repository contained the following data: * 1667 test plans * 1,000,000 test scripts * 1,000,000 test cases * 4,000,000 test case execution records * 4,000,000 test case results * 100,000 test suites * 5,000 work items(defects) * 6667 test environments * 20,000 test phases * 200 build definitions * 47,470 execution sequences * 100,000 test suite execution records * 500,000 test suite execution results * 33,333 build records * QM Database size = 310 GB * QM full text index size = 15 GB The artifact maintains the following associations: * each test plan is linked to 600 unique test cases, and 600 unique test scripts * each test suite contains 500 test cases In this test environment, the <b> Configuration Management </b> is not enabled. ---++ Appendix B: Methodology 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 which are separated into individual user groups within an RPT schedule. The settings of the RPT schedule is shown below: <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceScalabilityReportRQM603Release/userload.png" /> ---+++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>Test plan create, Browse test plan and test case, Browse test script, Simple test plan copy, Defect search, View dashboard</td> </tr> <tr> <td>Test Lead</td> <td align="center">19</td> <td>Edit Test Environments, Edit test plan, Create test case, Bulk edit of test cases, Full text search, Browse test script, Test Execution, Defect search</td> </tr> <tr> <td>Tester</td> <td align="center">68</td> <td>Defect create, Defect modify, Defect search, Edit test case, Create test script, Edit test script, Test Execution, Browse test execution record</td> </tr> <tr> <td>Dashboard Viewer</td> <td align="center">5</td> <td>View dashboard(with login and logout)</td> </tr> </tbody> </table> *Test Cases* #TestCases <table class="gray-table"> <tbody> <tr> <th align="center" height="40"><b>Use Role</b></th> <th align="left" height="40"><b>Percentage of the user role</b></th> <th align="left" height="40"><b>Sequence of Operations</b></th> </tr> <tr> <td rowspan=6>QE Manager</td> <td align="center">1</td> <td>[[#TestPlanCreate][Test plan create]]:user creates test plan, then adds description, business objectives, test objectives, 2 test schedules, test estimate quality objectives and entry and exit criteria.</td> </tr> <tr> <td align="center">26</td> <td>[[#BrowseTestPlansAndTestCases][Browse test plans and test cases]]: user browses assets by: View Test Plans, then configure View Builder for name search; open test plan found, review various sections, then close. Search for test case by name, opens test case found, review various sections, then close.</td> </tr> <tr> <td align="center">26</td> <td>[[#BrowseTestScript][Browse test script]]: user search for test script by name, open it, reviews it, then closes.</td> </tr> <tr> <td align="center">1</td> <td>[[#SimpleTestPlanCopy][Simple test plan copy]]: user search test plan by name, then select one, then make a copy.</td> </tr> <tr> <td align="center">23</td> <td>[[#DefectSearch][Defect search]]: user searches for specific defect by number, user reviews the defect (pause), then closes.</td> </tr> <tr> <td align="center">20</td> <td>[[#ViewDashboard][View Dashboard]]: user views dashboard</td> </tr> <tr> <td rowspan=8>Test Lead</td> <td align="center">8</td> <td>[[#EditTestEnvironment][Edit Test Environment]]: user lists all test environments, and then selects one of the environments and modifies it.</td> </tr> <tr> <td align="center">15</td> <td>[[#EditTestPlan][Edit test plan]]: list all test plans; from query result, open a test plan for editing, add a test case to the test plan, a few other sections of the test plan are edited and then the test plan is saved.</td> </tr> <tr> <td align="center">4</td> <td>[[#TestCaseCreate][Create test case]]: user create test case by: opening the Create Test Case page, enters data for a new test case, and then saves the test case.</td> </tr> <tr> <td align="center">1</td> <td>[[#BulkEditofTestCases][Bulk edit of test cases]]: user searches for test cases with root name and edits all found with owner change.</td> </tr> <tr> <td align="center">3</td> <td>[[#FullTextSearch][Full text search]]: user does a full text search of all assets in repository using root name, then opens one of found items.</td> </tr> <tr> <td align="center">32</td> <td>[[#BrowseTestScript][Browse test script]]: user search for test script by name, open it, reviews it, then closes.</td> </tr> <tr> <td align="center">26</td> <td>[[#TestExecutionFor4Steps][Test Execution]]: selects View Test Execution Records, by name, starts execution, enters pass/fail verdict, reviews results, sets points then saves. </td> </tr> <tr> <td align="center">11</td> <td>[[#DefectSearch][Defect search]]: user searches for specific defect by number, user reviews the defect (pause), then closes.</td> </tr> <tr> <td rowspan=8>Tester</td> <td align="center">8</td> <td>[[#CreateDefect][Defect create]]: user creates defect by: opening the Create Defect page, enters data for a new defect, and then saves the defect. </td> </tr> <tr> <td align="center">5</td> <td>[[#DefectModify][Defect modify]]: user searches for specific defect by number, modifies it then saves it.</td> </tr> <tr> <td align="center">14</td> <td>[[#DefectSearch][Defect search]]: user searches for specific defect by number, user reviews the defect (pause), then closes.</td> </tr> <tr> <td align="center">6</td> <td>[[#EditTestCase][Edit test case]]: user searches Test Case by name, the test case is then opened in the editor, then a test script is added to the test case (user clicks next a few times (server size paging feature) before selecting test script), The test case is then saved.</td> </tr> <tr> <td align="center">4</td> <td>[[#TestScriptCreate][Create test script]]: user creates test case by: selecting Create Test Script page, enters data for a new test script, and then saves the test script. </td> </tr> <tr> <td align="center">8</td> <td>[[#EditTestScript][Edit test script]]: user selects Test Script by name. test script then opened for editing, modified and then saved.</td> </tr> <tr> <td align="center">42</td> <td>[[#TestExecutionFor4Steps][Test Execution]]: selects View Test Execution Records, by name, starts execution, enters pass/fail verdict, reviews results, sets points then saves. </td> </tr> <tr> <td align="center">7</td> <td>[[#TestExecutionRecordBrowsing][Browse test execution record]]: user browses TERs by: name, then selects the TER and opens the most recent results.</td> </tr> <tr> <td>Dashboard Viewer</td> <td align="center">100</td> <td>[[#ViewDashboardWithLogin][View dashboard(with login and logout)]]: user logs in, views dashboard, then logs out. This user provides some login/logout behavior to the workload </td> </tr> </tbody> </table> ---+++Response time comparison The page performance is measured as mean value (or average) of its response time in the result data. For the majority of the pages under tests, there is little variation between runs, and the mean values are close to median in the sample for the load. ---++ Appendix C: Detailed performance results #DetailedResults ---+++Average page response time comparison breakdown For all usecase comparison charts, the unit is millisecond, and for the data, smaller is better. #CreateDefect Create Defect <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/createDefect.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #TestPlanCreate Create Test Plan <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/createTestPlan.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #TestCaseCreate Create Test Case <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/createTestCase.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #TestScriptCreate Create Test Script <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/createTestScript.png"/> [[#TestCases][Back to Test Cases & workload characterization]] #BrowseTestPlansAndTestCases Browse Test Plans & Test Cases <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/browseTPsTCs.png"/> [[#TestCases][Back to Test Cases & workload characterization]] #BrowseTestScript Browse Test Scripts <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/browseTestScripts.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #BulkEditofTestCases Bulk Edit of Test Cases <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/bulkEditTC.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #DefectSearch Defect Search <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/searchDefect.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #DefectModify Defect Modify <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/modifyDefect.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #EditTestCase Edit Test Case <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/editTestCase.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #EditTestEnvironment Edit Test Environment <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/editTestEnv.png"/> [[#TestCases][Back to Test Cases & workload characterization]] #EditTestPlan Edit Test Plan <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/editTestPlan.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #EditTestScript Edit Test Script <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/editTestScript.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #FullTextSearch Full Text Search <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/fullTextSearch.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #SimpleTestPlanCopy Simple Test Plan Copy <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/simpleCopy.png"/> [[#TestCases][Back to Test Cases & workload characterization]] #TestExecutionFor4Steps Test Execution For 4 Steps <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/executeTestSteps4.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #TestExecutionRecordBrowsing Test Execution Record Browsing <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/browseTERs.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #ViewDashboard View Dashboard <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/viewDashboard.png" /> [[#TestCases][Back to Test Cases & workload characterization]] #ViewDashboardWithLogin View Dashboard with Login <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/viewDashboardDV.png" /> [[#TestCases][Back to Test Cases & workload characterization]] ---+++RPT network transfer comparison <img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/RPT_network_v604_vs_v603.png" /> ---+++RPT script execution composition The script execution breakdown is similar to the scalability test: [[https://jazz.net/wiki/bin/view/Deployment/CollaborativeLifecycleManagementPerformanceScalabilityReportRQM603Release#RPT_script_executions][RPT script executions breakdown in scalability test of 6.0.3]] ---+++Resource utilization %TABLE{ sort="off" headerbg="#3399FF" cellpadding="2" cellspacing="2" dataalign="center" caption="OS resource utilization 6.0.4 vs 6.0.3 - overview" tableborder="2" tableframe="border" tablerules="none"}% ||6.0.4 vs 6.0.3| |CPU|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/CPU_v604_vs_v603.png" />| |Disk|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Disk_v604_vs_v603.png" />| |Memory|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Mem_v604_vs_v603.png" />| |Network|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Network_v604_vs_v603.png" />| %TABLE{ sort="off" headerbg="#3399FF" cellpadding="2" cellspacing="2" dataalign="center" caption="QM server resource utilization 6.0.4 vs 6.0.3" tableborder="2" tableframe="border" tablerules="none"}% ||6.0.4|6.0.3| |CPU|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/CPU_QM_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/CPU_QM_CLM603.png" />| |Disk|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Disk_QM_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Disk_QM_CLM603.png" />| |Memory|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Mem_QM_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Mem_QM_CLM603.png"/>| |Network|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Network_QM_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Network_QM_CLM603.png"/>| %TABLE{ sort="off" headerbg="#3399FF" cellpadding="2" cellspacing="2" dataalign="center" caption="DB server resource utilization 6.0.4 vs 6.0.3" tableborder="2" tableframe="border" tablerules="none"}% ||6.0.4|6.0.3| |CPU|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/CPU_DB_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/CPU_DB_CLM603.png"/>| |Disk|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Disk_DB_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Disk_DB_CLM603.png"/>| |Memory|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Mem_DB_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Mem_DB_CLM603.png"/>| |Network|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Network_DB_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/Network_DB_CLM603.png"/>| ---+++Garbage collection - JVM GC Chart For JVM parameter please refer to [[#Appendix_D_Key_configuration_par][Appendix D: Key configuration parameters]] Verbose garbage collection is enabled to log the GC activities. These GC logs showed very little variation between runs. There is also no discernible difference between versions. 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 JVM Garbage Collection Charts 6.0.4 vs 6.0.3" tableborder="2" tableframe="border" tablerules="none"}% ||6.0.4|6.0.3| |QM|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/GC_QM_CLM604.png" />|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/GC_QM_CLM603.png" />| |JTS|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/GC_JTS_CLM604.png"/>|<img src="https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPerformanceReportRQM604Release/GC_JTS_CLM603.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;">IBM HTTP Server for !WebSphere Application Server</td> <td style="vertical-align: top;">8.5.5.9</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 = 25 *OS Configuration*: * max user processes = unlimited </td> </tr> <tr> <td style="vertical-align: top;">IBM !WebSphere Application Server Network Deployment</td> <td style="vertical-align: top;">8.5.5.9</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 -Xss786K -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -verbose:gc -Xverbosegclog:gc.log -XX:MaxDirectMemorySize=1G </verbatim> *SDK version:* * IBM WebSphere SDK for Java Technology Edition Version 7.1.3.40 *Thread pools:* * Maximum !WebContainer = Minimum !WebContainer = 500 *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>ESE 10.1.0.5</td> <td> </td> </tr> <tr> <td>LDAP server</td> <td> </td> <td> </td> </tr> <tr> <td>License server</td> <td> </td> <td>N/A</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> -------------------- ---++++!! About the authors: Main.HongyanHuo is a performance engineer focusing on the scalability of products in the Collaborative Lifecycle Management family. ---++++!! Related topics: [[CollaborativeLifecycleManagementPerformanceScalabilityReportRQM603Release][Collaborative Lifecycle Management performance and scalability report: Rational Quality Manager 6.0.3 release]] -------------------- ---+++++!! 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>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r9
<
r8
<
r7
<
r6
<
r5
|
M
ore topic actions
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
.