Load testing for tuning

The performance testing process It's an activity aimed at verifying, through load testing, whether and to what extent an application is able to deliver a predetermined service level on a specific hardware/software architecture, before its release into production.
The main purpose of load testing for tuning is to systematically improve every level of a complex IT system to ensure high quality standards in terms of performance.
This objective is achieved through a cyclical process that involves: loading the system, identifying the components that limit its performance, and to eliminate bottlenecks through tuning and upgrade interventions.
The first part of the course describes a methodology that allows for the systematisation of the performance testing process. Furthermore, the different phases that make up the testing process are identified and detailed. For each phase, organisational aspects, information flows, and the documents underpinning the process are considered.
The second part of the course focuses on two types of load tests: the Load test, which allows the system's performance to be assessed under normal operating conditions, and it stress test, which allows for the assessment of how the system performs under maximum load conditions.
During the course, real-life cases are shown, using as a reference tool LoadRunner® by HP.

Home » Course List  » Load testing for tuning

Contents

Planning

Define the service level objectives

- The testing process for the inspection

Test design, environment setup, detailed design, test execution.

- Validation of the results
- The limits of a testing procedure, common errors, a safe approach
Types of load testing

Load testing and stress testing

- Stress test execution methods
- Main problems under load

Memory leak, resource locking, transactional limit, bandwidth limit, hardware bottleneck, software bottleneck.

- The tuning test process

Test design, environment setup, detailed design, test execution and results analysis, HW/SW tuning, activity reporting.

3 days

Prerequisites

Nobody.


Recipients

Information Systems Managers

Application owners

Quality management and control officers

Scroll to Top