Hello
cloudsql-proxy uses SSL and each connection go through the SSL handshake which adds up some delay, however on the other hand direct connection to the Cloud SQL (with SSL disabled) work without the SSL overhead providing less connection time. Apart from the mentioned possible reasons, I would suggest checking performance on pods to ensure it is not hitting and cpu/memory bottleneck as resource constraints on the pods could cause latency with SSL handshakes and such.
On Thursday, May 31, 2018 at 2:57:28 PM UTC-4, Daniel Alm wrote:
-- cloudsql-proxy uses SSL and each connection go through the SSL handshake which adds up some delay, however on the other hand direct connection to the Cloud SQL (with SSL disabled) work without the SSL overhead providing less connection time. Apart from the mentioned possible reasons, I would suggest checking performance on pods to ensure it is not hitting and cpu/memory bottleneck as resource constraints on the pods could cause latency with SSL handshakes and such.
On Thursday, May 31, 2018 at 2:57:28 PM UTC-4, Daniel Alm wrote:
Hello, thanks for your reply. My issue is NOT related to the SSL handshake. I am ALWAYS using connection pooling, yet latency is much higher when connecting via the proxy as opposed to direct connections, even after the connection pools have been filled. Could you please take another look as to what could be going one here?
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/aee9bd34-1233-4b9b-8a29-3638d3ea26df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment