Edit
Attach
P
rintable
r1 - 2014-11-21 - 15:26:50 -
JorgeAlbertoDiaz
You are here:
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RTCSystemZPerformanceTesting
>
RTCEEWorkloadTests
>
RTCEEWorkloadTestScenario1Report
<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%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"> RTCEE Performance Testing: EE Workload Scenario Scenario 1 Test Report %DKGRAY% Authors: [[Main.JorgeAlbertoDiaz][Jorge Diaz]] </br> Date: Nov 21st, 2014 </br> Build basis: Rational Team Concert 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 report gathers the result of the execution of the ---++ Disclaimer %INCLUDE{"PerformanceDatasheetDisclaimer"}% ---++ Findings ---++ Topology The tests are executed in a Single Tier Topology infrastructure like the one in the following diagram: %INCLUDE{"RTCEETestingTopologies" section="DualTierZ"}% ---+++ Test Topology Parameterization The following system configuration is used in the execution of this particular scenario variant: <table class="gray-table"> <tr> <th><strong>Test Environment</strong></th> <th>Configuration</th> <th>Model</th> <th>MSU</th> </tr> <tr> <td><strong>RTC Server</strong></td> <td>Operating System & Version: z/OS 01.12.00 </br> System Resource : 10 GB Storage, 2 CPs (1000 mips, CPU type : 2097.710) </br> CALM: 5.0 GA, 4 GB heap size </br> WAS: 8.5.5.1 </br> </td> <td>E12</td> <td/> </tr> <tr> <td><strong>Build Forge Agent & DB2z</strong></td> <td>Operating System & Version: z/OS 01.12.00</br> System Resource: 6 GB Storage, 4 CPs (2000 mips, CPU type : 2097.710) </br> Build System Toolkit: 5.0 GA </br> DB2: 10.1.0.0 </br> </td> <td>E12</td> <td>513</td> </tr> </table> ---++ Results * For 8 hours long run of scenario1, 46 times(iterations) concurrent builds have been launched, total 1288 personal builds and 44 team builds have been processed successfully. <table class="gray-table"> <tr> <th>Start Time</th> <th>End Time</th> <th>Concurrent Request Times</th> <th>Concurrent Users Each Time</th> <th>Total Personal Builds Num</th> <th>Team Build Request Times</th> <th>Total Team Builds Num</th> </tr> <tr> <td>8/16/2014 11:30:50 AM</td> <td>8/16/2014 7:34:38 PM</td> <td>46</td> <td>28</td> <td>1288</td> <td>4</td> <td>40<td> </tr> </table> * Personal build time/aversage build time of concurrent builds in 8 hours test; <table class="gray-table"> <tr> <th>Build Definition</th> <th>Build duration of Personal Build</th> </tr> <tr> <td>Build Definition 1 - 2</td> <td>22 seconds - 4 minutes 22 seconds, average 2 minutes<td> </tr> <tr> <td>Build Definition 3 - 5</td> <td>30 seconds - 4 minutes 53 seconds, average 2 minutes 30 seconds<td> </tr> <tr> <td>Build Definition 6 - 10</td> <td>29 seconds - 3 minutes 43 seconds, average 2 minutes 10 seconds<td> </tr> </table> * No build(both personal and team build) fails in EE workload scenario 1 test; * %RED%CPU usage of CLM server is < 60% %ENDCOLOR%;<br/> <img src="%ATTACHURLPATH%/avganalysisOfclmserver.jpg"/> <img src="%ATTACHURLPATH%/cpudsad_clmserver.jpg"> * %RED%CPU usage of BST & DB2z is < 60% %ENDCOLOR%;<br/> <img src="%ATTACHURLPATH%/avganalysisOfbst.jpg"/> <img src="%ATTACHURLPATH%/cpudsad_bst.jpg"> * %RED%CPU usage of DB2z is smoothly under 6% %ENDCOLOR%;<br/> <img src="%ATTACHURLPATH%/cpuOfDB2z.jpg"> * 140.4 Contributors are simulated in 2nd run - Overall Count Attempted Tasks For Run = 23990 * Size of repository volume don't increases in 8 hours exeuction(compare end with start condition). * Indice incremental rate: <table class="gray-table"> <tr> <th>Indice Directory Name</th> <th>Before execution</th> <th>After execution</th> <th>Incresed Rate</th> </tr> <tr> <td>_Indices</td> <td>2115620</td> <td>2242828</td> <td>6.01%</td> </tr> <tr> <td>./jfs-rdfhistory</td> <td>308</td> <td>424</td> <td>37.66%</td> </tr> <tr> <td>./jfs-rdfindex</td> <td>1986436</td> <td>2112940</td> <td>6.37%</td> </tr> <tr> <td>./jfs-texthistory</td> <td>52</td> <td>252</td> <td>0.00%</td> </tr> <tr> <td>./jfs-textindex</td> <td>128816</td> <td>129404</td> <td>0.46%</td> </tr> </table> ---++++!! About the authors Main.JorgeAlbertoDiaz -------------------- ---+++++!! 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>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r2
<
r1
|
More topic actions...
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
NOTE: Please use the Sandbox web for testing
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
.