Every OCPP charge point maintains a persistent WebSocket connection to your CPMS. At scale, that means managing many long-lived connections, each sending periodic heartbeats, status notifications, and meter values.
Most CPMS platforms are tested with 10-50 charge points. When they hit 500+ in production, connection timeouts, message queue backlogs, and database write bottlenecks start appearing.
Choose from vendor-style charge point model profiles or create custom profiles. Set the connection count for the scale you need to validate.
Set realistic session distributions: peak hours, concurrent starts, rapid session turnover, overnight slow charging.
All virtual charge points connect simultaneously via WebSocket. Each sends realistic OCPP messages.
Real-time dashboards show connection success rate, latency percentiles (p50, p95, p99), throughput, and error rates.
OCPP load testing measures how a Charge Station Management System (CPMS) 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. At scale (500+ charge points), many CPMS platforms experience connection pool exhaustion, message processing latency spikes, and database write contention. OCPPLab enables high-volume virtual charge point load testing. It measures connection time, message latency (p50, p95, p99), throughput, and error rates, so teams find breaking points before production deployment.
Run high-volume virtual charge point checks before production rollout.
Last updated: