Concurrent WS Open connectins
I'm building an app that may have a lot of peoples connections open (aka a game state which they are reading). The concurrent mutations are low but how many concurrent listeners can convex / convex queries handle?
5 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
i saw thousands in a post earlier, but how many like 100s of thousands or 10s? I'm trying to prepare for scale
the solution im evaluating is traditional postgres + electric sql vs Convex
it depends a lot on the specific query patterns
hanging idle connections is cheap
so most of the limits are about like query update rates and how many people are all subscribed to the same queries vs. different queries, and so on
yeah lets say i have a game state query which is what im mainly updating
so pretty much all my users are subbed to one query
which controls the realtime nature of my app
we've definitely had 10s of thousands of people connected at once to things. especially b/c the compute load is pretty light there due to caching. less sure about 100s of thousands. you could prop the open source image up on a beefy machine and see how it does! just up all your ulimits