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
I use databases with asyncpg and database I'm connecting to is located 250ms away.
Every DB query ends up doing an extra 250ms round trip due to asyncpg executing a reset query on connection release back to the connection pool.
This results in a huge performance hit in my case, is there any way to return the result first and do connection release cleanups in the background? Or any other way around it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Kind people of internet, I have a situation!
I use databases with asyncpg and database I'm connecting to is located 250ms away.
Every DB query ends up doing an extra 250ms round trip due to asyncpg executing a reset query on connection release back to the connection pool.
This results in a huge performance hit in my case, is there any way to return the result first and do connection release cleanups in the background? Or any other way around it?
Any help will be much appreciated.
Cheers,
Leo
Beta Was this translation helpful? Give feedback.
All reactions