phoenix2x
phoenix2x
Thanks for the quick follow up:) 1. we use [bun](https://github.com/uptrace/bun) which uses database/sql pool under the hood 2. `MaxIdleConns` and `MaxOpenConns` = 20, `ConnMaxIdleTime` = 15m, `ConnMaxLifetime` = 1h 3....
It's a single Postgres instance in this test. As I can see from the internal spans all the time is spent in `cloud.google.com/go/cloudsqlconn/internal.Connect` span. `cloud.google.com/go/cloudsqlconn/internal.InstanceInfo` stays extremely fast and there...
Yes, we use nightly load testing to prevent regressions. As soon as we switched from rds to GCP SQL we noticed this issue. The load test is just a script...
Hi @enocom, This is very interesting, thank you:) Is this supposed to target Server Side Proxy on port 3307 or native 5432?
Nice, we should definitely give it a try.