Connection Keep Alive

[StanGirard]

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.

[juancarlospaco]

is it really required? 🤔

• https://serverfault.com/a/790302
• https://g.co/gemini/share/5915292ee17d

Also, it should be ON by default whatsoever, because it is hardcoded:

• https://github.com/encode/httpx/blob/4b85e6c3898b94e686b427afd83138c87520b479/httpx/_client.py#L292
• https://github.com/encode/httpx/blob/4b85e6c3898b94e686b427afd83138c87520b479/CHANGELOG.md?plain=1#L1068
• https://github.com/encode/httpx/blob/4b85e6c3898b94e686b427afd83138c87520b479/tests/client/test_headers.py#L38

It is interesting nevertheless, will keep investigating...

[StanGirard]

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.

[juancarlospaco]

I can confirm it is not the "keep-alive" by itself IMHO, something funny is happening somehow, will keep investigating...

[StanGirard]

@juancarlospaco Thanks Juan! Let me know if i can help anyhow