[kelvich]

Yes, exploring http/3 is on the roadmap. One of the learnings for us was the fact that v8 is quite good with caching open TCP connection; For consecutive queries the same TCP+TLS session is being reused. Even when queries are sent from unrelated V8 isolates.

[KingMob]

In that case, HTTP/3 might actually perform worse for you than HTTP/2, unless v8 caches QUIC conns as well.

The major advantage you'd get with HTTP/3 and QUIC is fewer round trips to start a conn, and no head-of-line blocking like with TCP (which might be irrelevant if the Pg protocol doesn't use simultaneous streams, dunno).

The disadvantage is you'd have to support QUIC in your proxy (and gmac said your server lib doesn't support it yet.)

Don't get hung up on HTTP/3 as the latest and greatest, HTTP/2 is probably still an improvement for you.

> Even when queries are sent from unrelated V8 isolates.

Heh, I've definitely written a few AWS Lambdas that exploited this sort of behavior. "Sure, this resource might not exist. But I'm going to check, just in case..."

[VWWHFSfQ]

Are you saying that V8 is reusing TCP connections between different browser tabs and websites? Seems like a timing/side-channel attack could be done with that.

[gmac]

No, this is in a serverless environment running on V8 isolates (specifically, Vercel Edge Functions).

[VWWHFSfQ]

Oh I see. Not Chrome v8