~~EditAttach~~Printable

r1 - 2014-09-01 - 10:23:53 - JorgeAlbertoDiazYou are here: TWiki >

Deployment Web > DeploymentPlanningAndDesign > PerformanceDatasheetsAndSizingGuidelines > RTCSystemZPerformanceTesting > RTCEEConcBuildTests

RTCEE Performance Testing: Concurrent Builds Scenario

Authors: Jorge Diaz
Build basis: RTC 4.x

Page contents

This scenario is consider one of the "Additional" ones, as it's not part of the standard set of test scenarios executed every time (i.e. in every release), as part of the RTCEE Benchmark Tests.
The scenario targets the concurrent execution of several personal builds and a team build.

Scenario Detailed Description

Following the detail of the different steps that are performed for testing this scenario:

Test Steps	Description
1. Perform enterprise dependency build with Mortgageapplicationx250 2. Run personal build for Mortgage Application 250 after changing ALL copybooks 3. Run personal build for Mortgage Application 250 without any changes 4. Run another Mortgage Application 250 enterprise build without any changes. 5. Run ONE Mortgage Application 250 enterprise build and FIVE personal builds from the same enterprise builds with different repository workspace, changing ALL copybooks	After a first complete build of all the programs, different sets of changes and personal builds are performed. The final step of the test consists of emulating five users changing all the copybooks and running personal builds in parallel to check the performance and resources impact when concurrency is added.

Test Steps

Description

1. Perform enterprise dependency build with Mortgageapplicationx250
2. Run personal build for Mortgage Application 250 after changing ALL copybooks
3. Run personal build for Mortgage Application 250 without any changes
4. Run another Mortgage Application 250 enterprise build without any changes.
5. Run ONE Mortgage Application 250 enterprise build and FIVE personal builds from the same enterprise builds with different repository workspace, changing ALL copybooks

After a first complete build of all the programs, different sets of changes and personal builds are performed.
The final step of the test consists of emulating five users changing all the copybooks and running personal builds in parallel to check the performance and resources impact when concurrency is added.

Test Topologies

The following topologies are being used for the execution of this scenario in order to test the performance and gather relevant data.

Single Tier Topology: zLinux

Test Reports

Fill with a brief introduction and links to relevant data

External links:

Additional contributors:

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.