Base Motivation

Why you need this knowledge

• Approach a load test result correctly
• See things, other might not see
• Conclude the right things

• Make your case
• Know the direction of future testing
• Trust your own work!

Being able to draw ideas out of charts and numbers is cool.

Question to Ask

What you might have to ask first

• Was the setup correct?
• Is the result expected?
• Does it prove my point?
• Is there anything known or unknown in the result?

• What can I learn from the test?
• What do I have to do next?
• Was it my fault?

Don't overthink!

Load Setup

• Transactions: Right scenarios?
• Measurement Period
• Thinktime

• Arrival Rate setting does not guarantee, hence you cannot check anything here

Concurrent User Chart

• Ramp up visible?
• Any spikes up or down?
• How nervous is the user chart (arrival rate)?
• Max users = Max number of concurrently used session = Max possible concurrent requests

Requests

• Count: Any spikes?
• Ramp up visible?
• Requests/s in the ballpark?
• Runtime patterns or spikes?
• Waves?

Errors

• Do we have any errors?
• Do we have a pattern?
• Did we expect errors?

Misc

• Right timezone?
• PXX set correctly?
• SLA set correctly?
• Right time frame?

• Links to results?
• Any external data configured?

In good shape?

• Overall CPU per box <40%
• Per Agent CPU
• Memory curve nice and steady, not hitting max
• GC information
• All cool? Move on.

Charts

What you should look for in charts

• Patterns
• Spikes
• Matching failure and response times

• See cache problems
• See memory issues
• See socket or other resource issues
• See third party problems