-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Keep Alive #783
Comments
is it really required? 🤔 Also, it should be ON by default whatsoever, because it is hardcoded:
It is interesting nevertheless, will keep investigating... |
Hey @juancarlospaco, I've been battling with it for almost a week. Going with direct connection to the database with RAW SQL queries makes it way faster. I looked into Kong, it should be around 8ms of latency not 40ms. There might be something funny happening. Here you can see the time when I do queries directly to database and when using the python sdk. Would love to help you investigate. Both my backend and my supabase are in Ireland on AWS. |
I can confirm it is not the "keep-alive" by itself IMHO, something funny is happening somehow, will keep investigating... |
@juancarlospaco Thanks Juan! Let me know if i can help anyhow |
Hello @juancarlospaco, any update of this issue ? |
As explained at #783 (comment) Make sure you are not running too old libs, or running in an env in debug mode In the latest version of the clients, it has HTTP2 enabled which ignores all of this and uses persistent connections by default. |
Closing as there has been no reply from OP for over a month. |
Hey !
It seems that the TLS Handshake happens every query.
Implementing a Keep-alive and keeping the connection alive would save around 60ms per query.
The text was updated successfully, but these errors were encountered: