Looking for advice on Edge Connector behavior under load. We are running a stress test to validate WebSocket capacity on a BYOC setup. The environment is Genesys Cloud with a custom Edge Connector deployed in AWS ap-southeast-1.
Using JMeter with 500 concurrent users connecting via WebSocket. The ramp-up is 60 seconds. Everything works fine up to about 200 concurrent connections. After that, the connection success rate drops significantly. We see a lot of connection timeouts and occasional 502 Bad Gateway responses from the Edge.
The Edge logs show no obvious errors, just high latency. We are using the standard Genesys Edge Connector image.
“The Edge Connector acts as a reverse proxy… It is designed to handle high throughput…”
We read this in the docs but it doesn’t help with our specific issue. Is there a specific setting in the Edge Connector config or the JMeter script that we are missing? We want to push to 1000 concurrent connections. The latency spikes are happening before we hit the Genesys Cloud API rate limits. We are not seeing any 429s yet. Just connection failures.
Any tips on tuning the Edge Connector for higher concurrency? We are new to this so any help is appreciated. We are based in Singapore so timezone is UTC+8. We are testing during off-peak hours.