1. 􀁺What is OpenSTA?

2. 􀁺How OpenSTA Works

3. 􀁺Creating Scripts

4. 􀁺OpenSTA Collectors

5. 􀁺Creating Tests

6. 􀁺Running Tests

7. 􀁺Analyzing Results

What is OpenSTA?

1. 􀁺OpenSTA HTTP/S Load

2. –Open System Testing Architecture

3. –Load testing is the only available module

4. 􀁺Open source software –freely distributed

5. 􀁺Enables performance testing of

6. –Web applications

7. –Other apps that use HTTP protocol

8. 􀁺Available at http://www.opensta.org

How OpenSTA Works

1. 􀁺Script Modeler: Create and edit scripts

2. 􀁺Commander: Create and run tests

3. 􀁺Name Server: Manages distributed machines

4. 􀁺Each virtual user is run in a separate thread

5. –Up to about 1500 VUsper machine

6. –Load can be generated from multiple machines

Creating Scripts

1. 􀁺Record interactions with a web server

2. –Gateway records requests and responses

3. –Can record HTTPS transactions

4. –Automatically captures cookies

5. –Saves original web content

6. 􀁺Add timers to measure tasks

7. 􀁺Modify submitted data

8. 􀁺Modify wait times

OpenSTA Scripts

1. 􀁺Scripts recorded in SCL language

2. –Fairly simple coding language

3. –Limited built in functions

4. –Can write own functions in include files

5. 􀁺Good variable management

6. –Different variable scopes

7. –Random or sequential lists

8. –Variable generation

OpenSTA Collectors

1. 􀁺Able to monitor performance during tests

2. 􀁺For Windows servers uses standard Performance Monitor

3. 􀁺SNMP collectors for other server OS

4. 􀁺Monitor during test run

5. 􀁺View and report on results afterward

Creating Tests

1. 􀁺Tests determine how to generate load

2. 􀁺One or more task groups in a test

3. –One or more scripts per task group

4. –One collector per task group

5. 􀁺For each task group configure

6. –Start and end settings

7. –Total virtual users and ramp up

8. –Machine to run on

Running Tests

1. 􀁺Start test from controller machine

2. –Each task group starts based on start settings

3. –Scripts automatically run on designated machines

4. 􀁺Monitor test execution during test run

5. –View collector and script data

6. –View number of VUs

7. 􀁺Stop test run

8. –Manually

9. –According to task group settings

Analyzing Results

1. 􀁺Numerous reports automatically generated

2. –Timer Values vs. Elapsed Time

3. –Timer Values vs. Number of Users

4. –HTTP Bytes/Sec

5. –HTTP Response Times vs. Number of Users

6. 􀁺Filter data in reports

7. 􀁺Export all data to Excel

8. –Analyze with Pivot Tables

9. –Compare with previous runs (not built in)

Conclusion

1. 􀁺OpenSTA capabilities

2. –Record and run against any HTTP/S server

3. –Distributed load generation

4. –Configurable user ramp-up

5. 􀁺Active user community

6. 􀁺Active development

7. 􀁺“Free”

8. 􀁺Radiumtesting@gmail.com