concurrency limits
can someone tell me about this concurrency? is that we can't let the user subscribe to same query after reaching the limits?
5 Replies
This is the number of functions that can run in parallel on that plan. It's rare to hit this problem purely from user requests because most Convex functions run very fast. This only happens when you have a very high traffic website, or if you're some massive external webhook type thing.
then what about the connections that are already connected? they will still be subscribed, right?
for example if I have a home feed that is subscribed by 10k users at the same time, will that also hit the limit?
These folks will get a result, they just may not get served at the same instant. Also if these queries are cached then it will bypass the query function entirely.
For customers serving the type of traffic you're describing, we recommend upgrading to the Pro plan, where we can work with you to adjust concurrency limits. We do this fairly regularly with some of our bigger customers.
ahhh nice! maybe there are some queue-like happening on the background right? so they need to wait for sometimes.
okay now i understand, i just planned to use convex to our company for making social media app
Yea, queue like. We've had customers with very high number of concurrent users on the platform. Do reach out with a pro-support ticket if you have very high concurrent needs.