Looking for advice on handling WebSocket connection limits when simulating high-concurrency agent load.
We are running a performance validation suite using JMeter 5.6 against the Genesys Cloud US1 environment. The goal is to validate call capacity planning by opening multiple WebSocket connections for real-time event streaming.
Currently pushing 200 concurrent threads against the /api/v2/analytics/events/realtime endpoint. The test triggers HTTP 429 Too Many Requests errors after approximately 15 seconds of execution. This happens even though the total connection count is well below the documented platform limits for our tier.
HTTP/1.1 429 Too Many Requests
Retry-After: 10
Content-Type: application/json
{
"errors": [
{
"code": "too_many_requests",
"message": "Rate limit exceeded for WebSocket connections"
}
]
}
The JMeter config uses standard keep-alive settings with a ramp-up period of 60 seconds. Is there a specific rate limit for WebSocket handshake requests that differs from standard REST API limits? Or is this a transient issue with the US1 region?
Any insights on adjusting JMeter parameters to avoid triggering these limits during load tests would be appreciated.