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
Hi there!
I'm using EDGE in conjunction with FastAPI and PostgreSQL, as well as pgbouncer for database connection pooling. When initializing the Registry, we specify poolclass=NullPool, since we're using pgbouncer to manage connections.
However, during production and load testing, we've noticed that EDGY is generating a high number of database connections, which is causing some issues. We'd like to find a way to reduce the number of connections so that we can optimize our system's performance.
We were wondering if there are any solutions available that could help us achieve this goal. For example, could we use decorators to ensure that all EDGY calls within an endpoint are executed within the same session? This would allow us to minimize the number of connection requests and improve the overall performance of our application.
The text was updated successfully, but these errors were encountered:
Edgy version: 0.24.2
Python version: 3.12
Hi there!
I'm using EDGE in conjunction with FastAPI and PostgreSQL, as well as pgbouncer for database connection pooling. When initializing the Registry, we specify poolclass=NullPool, since we're using pgbouncer to manage connections.
However, during production and load testing, we've noticed that EDGY is generating a high number of database connections, which is causing some issues. We'd like to find a way to reduce the number of connections so that we can optimize our system's performance.
We were wondering if there are any solutions available that could help us achieve this goal. For example, could we use decorators to ensure that all EDGY calls within an endpoint are executed within the same session? This would allow us to minimize the number of connection requests and improve the overall performance of our application.
The text was updated successfully, but these errors were encountered: