Hi.
I've been having issues with Bigtable performance and found using an app profile helped. It would be nice if the loadtest tool supported using an app profile.
Our Bigtable performance issue seems to be related to our setup. We have geo-replication with two regions, Sydney and us-central. We have cloud-run servers in those two regions. We often have very poor performance on our first requests (5s reads). By using an app profile and configuring the closest region to use the performance is down to ~50ms.
It seems like the default profile, which uses nearest server routing can take a bit of time to figure out where the nearest bigtable server is.
The loadtest module has been removed from the client library. We do not currently plan to support it any further. Instead, we are focusing on building a test suite to benchmark client library behavior.
Hi. I've been having issues with Bigtable performance and found using an app profile helped. It would be nice if the loadtest tool supported using an app profile.
I've already opened a PR to add this. https://github.com/googleapis/google-cloud-go/pull/5882
More Background
Our Bigtable performance issue seems to be related to our setup. We have geo-replication with two regions, Sydney and us-central. We have cloud-run servers in those two regions. We often have very poor performance on our first requests (5s reads). By using an app profile and configuring the closest region to use the performance is down to ~50ms. It seems like the default profile, which uses nearest server routing can take a bit of time to figure out where the nearest bigtable server is.