Hello Retool Team,
I am having some difficulty understanding the limitations of the Retool platform when creating applications for public use. We created an application and when we made it available for use by the community (about 70 people simultaneously), the server crashed. I have a bunissess subscription. In addition to the error displayed on the page, all application management is rendered invisible. Initially, we understood that it was a limit of 5,000 requests per minute to the DB. However, with 100 accesses with only 2 queries, the same situation occurs. Therefore, I would like to know how we can increase the number of requests and the number of simultaneous accesses.
Additional info: Retool Cloud
Welcome to the community, @Danilo_Santos! Thanks for reaching out.
I probably need a little more information and context to provide any specific insight. To start, can you share more information about the error that you mention seeing? And it sounds like you are using the provided RetoolDB for these queries - is that right? Can you also confirm your org's subdomain, for me? I want to make sure I'm looking at the right usage metrics.
In general, though, RetoolDB is intended to be a fairly lightweight solution for proof of concepts and other low traffic use cases. By default, each org is provided with 5GB of storage and the compute capacity to handle ~100 simultaneous connections. Note that the compute will also "hibernate" after a period of inactivity and take slightly longer to spin up when a new request comes in. Last but not least, we also enforce a rate limit of 1000 requests per minute.
Based on what you've described, it sounds like you're probably hitting the connection limit. Once you confirm your org's subdomain, I can bump up the dedicated compute to handle ~200 simultaneous connections. This is typically just a stopgap measure, though, and we recommend migrating to an external database solution that is intended to handle higher traffic.
Let me know if you have any additional questions!
