TLDR jegade has concerns about reaching the limit of 2000 concurrent connections on Chatwoot. sojan_official suggested there is no set limit and recommended scaling chatwoot horizontally by adding more nodes. Also gave a solution for loadtester blockage.
But it looks like 2000 are the current limit? We are using docker and the latest version
jegade did you follow this guide for the set up ? https://www.chatwoot.com/docs/self-hosted/deployment/docker
yes, but we use traefik as frontend
I don't think we are enforcing any limits. with single app /worker server set up like the one describe in above post, you could face bottleneck for concurrent connections may be at nginx level or so on. If you anticipate high traffic you can scale chatwoot horizontally by adding more web and worker nodes. examples https://www.chatwoot.com/docs/self-hosted/deployment/aws/ https://www.chatwoot.com/docs/self-hosted/deployment/helm-charts/ https://www.chatwoot.com/docs/self-hosted/deployment/heroku we run our SaaS version on heroku and we have been able to server much higher traffic with that set up
ok, i will start multiple nodes and test again
argh, [Rack::Attack][Blocked] my loadtester
jegade you can disable rack attack via the environment variable by setting `ENABLE_RACK_ATTACK` to false
jegade
Mon, 23 May 2022 19:16:54 UTCHi, we are using chatwoot for live stream support (Worship service). Whats the limit of concurrent connections for websocket and how could i increase it? At the moment we are about 2000-3000 concurrent viewers