You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Jet Admin opens a SQL connection immediately on the app start. This is causing issues on high load projects.
For example, I'm running an auto scalable Google Cloud Run project with gunicorn and concurrency set to 2, and with 100 parallel threads hummering my web site, the number of PostgreSQL connections is 300+. Disabling Jet Admin drops down the number of connections to ~100. There is no load coming towards Jet Admin endpoint at all, it just eats up a connection in every thread.
Is it possible to have Jet Admin only open a SQL connection when there's need for it? Such as on a first request to the API?
The text was updated successfully, but these errors were encountered:
Currently, Jet Admin opens a SQL connection immediately on the app start. This is causing issues on high load projects.
For example, I'm running an auto scalable Google Cloud Run project with gunicorn and concurrency set to 2, and with 100 parallel threads hummering my web site, the number of PostgreSQL connections is 300+. Disabling Jet Admin drops down the number of connections to ~100. There is no load coming towards Jet Admin endpoint at all, it just eats up a connection in every thread.
Is it possible to have Jet Admin only open a SQL connection when there's need for it? Such as on a first request to the API?
The text was updated successfully, but these errors were encountered: