You are here: » Thesis » Index 

Index

1 Introduction

2 Performance

• 2.1 definitions
• 2.1.1 performance
• 2.1.2 load test
• 2.1.3 stress test
• 2.1.4 benchmark test
• 2.2 the objective of the performance measurements
• 2.3 approach to the provision of performance
• 2.3.1 benchmarking
• 2.3.1.1 Mips und Flops
• 2.3.1.2 Whetstone-, dhrystone-, Linpack- und Livermore-Benchmarks
• 2.3.1.3 SPEC - "Standard Performance Evaluation Corporation" [10]
• 2.3.2 Black-box-testing
• 2.3.3 White-box-testing
• 2.3.4 Grey-Box-testing
• 2.3.5 Performance measurements of multi-layer architectures
• 2.3.5.1 definition - measure of performance
• 2.3.5.2 expectancy definition
• 2.3.5.3 preparation
• 2.3.5.4 implementation of the tests
• 2.3.5.5 evaluation and analysis of results
• 2.4 significance of results
• 2.5 tools for testing and analysis

3 Load test tools

• 3.1 decision-making criteria
• 3.2 comparison features
• 3.2.1 supported systems, protocols
• 3.2.2 scenario support (request-flow)
• 3.2.3 parallel number of users (virtual users)
• 3.2.4 Distributed application (distributed)
• 3.2.5 test script production (recording)
• 3.2.6 monitoring of client and server
• 3.2.7 analysis capabilities
• 3.2.8 commercial vs. open-source
• 3.3 categorizing of the load test tools
• 3.3.1 commercial "General Purpose" tools
• 3.3.2 "middleware" tools
• 3.3.3 open-source
• 3.4 representation of some load testing tools
• 3.4.1 The Grinder [23]
• 3.4.1.1 overview
• 3.4.1.2 Supported systems, protocols
• 3.4.1.3 3.4.1.3 scenario support (request-flow)
• 3.4.1.4 parallel number of users (virtual users)
• 3.4.1.5 distributed application
• 3.4.1.6 test script production (recording)
• 3.4.1.7 monitoring of client and server
• 3.4.1.8 analysis capabilities
• 3.4.1.9 usability
• 3.4.2 Neotys Neoload [24]
• 3.4.2.1 overview
• 3.4.2.2 supported systems, protocols
• 3.4.2.3 scenario support (request-flow)
• 3.4.2.4 parallel number of users (virtual users)
• 3.4.2.5 distributed application
• 3.4.2.6 test script production (recording)
• 3.4.2.7 monitoring of client and server
• 3.4.2.8 analysis capabilities
• 3.4.2.9 usability
• 3.4.3 Segue SilkPerformer ® [25]
• 3.4.3.1 overview
• 3.4.3.2 supported systems, protocols
• 3.4.3.3 scenario support (request-flow)
• 3.4.3.4 parallel number of users (virtual users)
• 3.4.3.5 distributed application (distributed)
• 3.4.3.6 test script production (recording)
• 3.4.3.7 monitoring of client and server
• 3.4.3.8 analysis capabilities
• 3.4.3.9 usability
• 3.4.4 other load test tools
• 3.4.4.1 commercial "General Purpose" tools
• 3.4.4.2 "middleware" tools
• 3.4.4.3 "open-source" tools

4 Bottleneck analysis in multi-layer architectures

• 4.1 testing procedures in multi-layer architectures
• 4.1.1 example Web
• 4.1.2 Bottleneck analysis with the help of White-box testing
• 4.1.2.1 expressiveness of the correlated data
• 4.1.2.2 benefits
• 4.1.2.3 disadvantages
• 4.1.2.4 conclusion
• 4.1.3 Bottleneck analysis with the help of black box testing
• 4.1.4 Bottleneck analysis using Black-box testing and analysis hierarchies
• 4.1.4.1 benefits
• 4.1.4.2 disadvantages
• 4.1.4.3 conclusion
• 4.1.5 Bottleneck analysis with the help of Grey-box testing
• 4.1.5.1 benefits
• 4.1.5.2 disadvantages
• 4.1.5.3 conclusion
• 4.2 review of the methods ofBottleneckanalysis

5 Project Campus Management

• 5.1 Overview
• 5.2 architecture
• 5.3 expected data and user load
• 5.4 decisions for performance tests
• 5.5 planning of performance tests
• 5.5.1 qualitative differences
• 5.5.1.1 test without reservations
• 5.5.1.2 test with reservations
• 5.5.2 quantitative differences
• 5.5.3 local differences
• 5.6 test phase I
• 5.6.1 requirements
• 5.6.1.1 technical requirements
• 5.6.1.2 terminliche conditions
• 5.6.2 preparation
• 5.6.2.1 setting up the test environment
• 5.6.2.2 creation of the test data
• 5.6.3 creation of the test scenarios
• 5.6.3.1 structure of the test system
• 5.6.4 test implementation plan
• 5.6.5 implementation, evaluation and interpretation of the test phase I
• 5.6.5.1 test phase I - noise evaluation
• 5.6.5.2 test phase I - stress test v1.0
• 5.6.5.3 test phase I - stress test v2.0
• 5.6.5.4 test phase I - stress test v3.0 and the followings
• 5.6.5.5 test phase I - Troubleshooting
• 5.6.6 completion of the test phase I
• 5.7 test phase II
• 5.7.1 planning of performance testing
• 5.7.2 preparation
• 5.7.3 scheduling
• 5.7.3.1 determine the noise value
• 5.7.3.2 determination of the reference data
• 5.7.3.3 stress test
• 5.7.3.4 load testing
• 5.7.4 execution

6 Weiterführende Aufarbeitung der Ergebnisse

• 6.1 design of a database schema
• 6.1.1 identification of the data
• 6.1.1.1 configuration settings
• 6.1.1.2 global recorded values
• 6.1.1.3 recorded values ofrequeststo one side
• 6.2 processing of data
• 6.2.1 database model for test data collection
• 6.3 creating and preparing the database
• 6.4 import of collected data in the database
• 6.5 creation of queries to visualize
• 6.5.1 general queries to a test run
• 6.5.2 request-specific queries to a test run
• 6.5.3 queries for analysis using hierarchies
• 6.5.3.1 local hierarchy
• 6.5.3.2 qualitative hierarchy
• 6.5.3.3 quantitative hierarchy

7 Summary and Preview

8 table of figures

9 Literature

10 statement of authorship

Translated by Yahoo Babelfish Service