Performance testing
Performance testing at TestLine means JMeter load scenarios that show at what traffic your system slows down or stops responding. You get numbers: response times, throughput and the error threshold, before your customers find out.
- JMeter
- Grafana
- CI
What you get
- A traffic model based on production data or business assumptions
- JMeter scripts for key paths with parameterised data
- Load, stress and soak tests
- A report with response times (p50, p95, p99), throughput and bottlenecks
When it's worth it
Before a campaign or launch
You expect a traffic spike. Better to know in advance how much the system can handle.
The system slows down at peak
Users report slowness at certain hours. A test reproduces the problem under controlled conditions.
After an infrastructure change
Cloud migration, a new database, a configuration change. We compare results before and after.
When an SLA is in the contract
You have response time commitments. Testing shows whether you meet them.
How I work
- step 1
Traffic model
We agree on scenarios, user numbers and goals.
- step 2
Scripts
Preparing and verifying the JMeter scripts.
- step 3
Testing
Running the tests and monitoring the system.
- step 4
Report
Results, bottlenecks and recommendations.
Tools
- JMeter
- Grafana
- CI
Frequently asked questions
Which environment do we test on?
Ideally a production copy with similar resources. We test on production only by agreement and outside peak hours.
Will you find the cause of the slowdown?
I'll show where response times grow and at what load. We diagnose the code or database together with your developers.
Can performance tests run in CI?
Yes. A short performance test on every release catches response time regressions.
Got a release in a few weeks?
Describe your project in the form. I'll reply with questions about scope or an initial test plan.