Is it possible to increase the concurrent WebSocket connection limit on the BYOC edge when running high load JMeter scripts? hitting 429 errors at 500 concurrent threads on api/v2/architect/flows. thanks.
This happens because the default rate limiting on the Platform API endpoints, specifically for api/v2/architect/flows. The 429 status code isn’t necessarily a WebSocket limit issue but rather a request throttling mechanism kicking in when concurrent threads exceed the allowed quota.
For BYOC environments, you generally cannot dynamically increase these limits via configuration alone. The standard approach in JMeter is to implement a pacing strategy. Add a Constant Throughput Timer to your test plan. Set Calculate Throughput Based On to All active threads and limit it to roughly 60-100 requests per minute per user.
Also, ensure your WebSocket Sampler is reusing connections efficiently. If every thread opens a new connection, you hit the connection pool cap faster than the API rate limit. Check the Connection Pool Size setting in the JMeter HTTP Request Defaults. Lowering it to 10-20 with connection reuse enabled often stabilizes the load without triggering the gateway’s overflow protection.