OCPP load testing and stress testing
Why OCPP load testing matters
Every OCPP charge point maintains a persistent WebSocket connection to your CSMS. At scale, that means managing many long-lived connections, each sending periodic heartbeats, status notifications, and meter values.
A CSMS that works with a handful of test chargers can still fail once many connect at once. Connection timeouts, message queue backlogs, and database write bottlenecks often only show up under concurrent load.
Common failures at scale
- WebSocket connection pool exhaustion as connections grow
- Message processing latency spikes when many chargers send at once
- Database write contention on MeterValues and transactions
- Heartbeat timeout storms on network hiccups
- Memory leaks from improperly closed connections
- OCPP message queue overflow under sustained load
Pick a workflow and chargers
Pick one saved OCPP workflow and how many virtual chargers run it at once, from 1 to 100.
Set duration and ramp-up
Run for 10 to 600 seconds, with every charger starting at once or ramping up over a period you choose.
Run the test
Each virtual charger connects over WebSocket and repeats the workflow's OCPP messages until the run ends.
Analyze results
After the run, see iterations per minute, the check pass rate, connection failures, and p95 latency for each OCPP action, with the frames of failed steps.
What is OCPP load testing?
OCPP load testing measures how a Charging Station Management System (CSMS) performs under high volumes of concurrent charge point connections. Each OCPP charge point maintains a persistent WebSocket connection, sending heartbeats, status notifications, meter values, and transaction messages. Under concurrent load, CSMS platforms can hit connection pool exhaustion, message processing latency spikes, and database write contention. OCPPLab load mode runs one saved OCPP workflow on up to 100 virtual chargers at once for 10 to 600 seconds, with a constant or ramping start. Results show iterations per minute, the check pass rate, connection failures, and p95 latency per OCPP action.
Related resources
Find your breaking point before your customers do
Run up to 100 concurrent virtual chargers against your CSMS before production rollout.