Hey everyone,
I am running a load test on our BYOC Edge setup in the Singapore region to see how it handles concurrent WebSocket connections for a custom IVR flow. I am using JMeter 5.6.2 with the WebSocket plugin to simulate 500 simultaneous agents logging in and initiating calls.
The issue is that after about 200 concurrent connections, the wss://edges-us-east-1.aws.genesiscloud.com/... endpoint starts returning 504 Gateway Timeout errors. Before this, the latency is fine (around 50ms), but then it spikes to over 2000ms.
Here is my current JMeter thread group config:
- Ramp-up: 10 seconds
- Loop count: Forever
- WebSocket sampler connected to the edge endpoint
I checked the Genesys Cloud admin console, and the edge status shows as healthy. I am also not hitting the API rate limits because these are persistent WebSocket connections, not REST calls. However, I noticed that the lastActive timestamp in the edge status API stops updating for some connections when the latency spikes.
Is there a specific connection limit for BYOC edges that I am missing? Or is there a timeout setting I need to adjust in the JMeter script? I tried increasing the keep-alive interval, but it did not help.
Any help would be appreciated. I need to prove to my manager that the edge can handle at least 1000 concurrent connections without dropping packets.