1. SOFTWARE PERFORMANCE
ENGINEERINGSESSION-01
Vajirani Pathirana

2. PERFORMANCE ENGINEERING
TESTING
Do Performance Testers and
Performance Engineers perform the
same role?

3. There is a clear distinction between the services provided by a
Performance Tester and Performance Engineer.
Duties of performance tester
Design and execute a Performance Test Strategy and Plan
Build the automation suite and artefacts
 Build monitoring and metric gathering solutions
 Execute test and tuning cycles
 Analyze results against requirements
Reporting to business stakeholders

4. Duties of performance Engineer
Code reviews
Running up profilers
Investigating environment configurations
 Reviewing performance best practices
 Tuning and supplying remediation activities to performance problems.
 Performance Tester would be focused on delivering a performance quality
management solution
Performance Engineer analyze the outputs of the test metrics and provide
solutions to the development and infrastructure teams to ensure
performance problems are resolved.

5.  Software Performance Engineering (SPE) is a
systematic, quantitative approach to the cost-effective
development of software systems to meet performance
requirements.
SPE is a software-oriented approach that focuses on
architecture, design, and implementation choices.
SPE gives you the information you need to build
software that meets performance requirements on time
and within budget.
SPE continues through the detailed design, coding and
performance and load testing phases to predict and
manage the performance of the evolving software as well
as monitor and report actual performance versus

6. SPE METHODS
Performance data collection
Quantitative performance analysis techniques
Prediction strategies
Management of uncertainties
Data presentation and tracking
Performance testing
Stress and load testing
Model verification and validation
Critical success factors and performance design principles
Patterns and anti-patterns.

7. OLD
Many organizations have used a "fix-it-later" approach to
performance.
Performance problems detected on testing phase, were corrected by
adding additional hardware, tuning the software or both.

8. PERFORMANCE
Performance problems are rare
Hardware is fast and inexpensive
Responsive software costs too much to build
You can tune it later

9. ENGINEERING ALTERNATIVE
SPE uses model predictions to evaluate trade-offs in software
functions versus hardware costs.
 The models assist developers in controlling resource requirements
by selecting architecture and design alternatives with acceptable
performance characteristics.
They aid in tracking performance throughout the development
process and prevent problems from surfacing late in the life cycle

10. IS SPE VIABLE FOR YOUR PROJECTS?
You can deliver the application on time and within budget while
meeting your performance requirements - with the first release.
You can know the hardware capacity requirements for your new
application before it is developed.
Architects know that their architecture will support performance
requirements before committing to code.
Project managers can track the status of performance while the
software is being developed.
Risks to achieving performance requirements are identified and
addressed early in the process, saving both time and money.

11. SPE is language and platform independent.
SPE uses simple models of software processing with the goal of
using the simplest possible model that identifies problems with the
system architecture, design, or implementation plans.
SPE can be easily integrated into the software development process.