Bigtable Cold Starts

Hello -

I’m designing an API for usage in a web application, and I decided to use Cloud Bigtable for fast response times. “Cold starts” are a known issue with bigtable, and I’m happy to accept that trade off. However, I feel as if I’ve been experiencing cold starts much longer than typical.

My research tells me most cold starts are 500ms or less, yet I’ve been consistently experiencing cold starts of ~10s.

I don’t anticipate this will be an issue in production, as the web app will be served with GKE in the same region as the Bigtable instance, but I do want to inquire and see if I am doing anything wrong.

For context, I am located in Montreal, Canada, and the Bigtable instance is located in South Carolina, USA. A colleague in Pittsburgh doesn’t experience these abnormally long cold starts.

Let me know if there’s any other information I can provide.

Hi @bsummy ,

Welcome to Google Cloud Community!

To answer your question, the ~10-second latency you’re experiencing from Montreal, while your colleague in Pittsburgh sees much faster initial responses, most probably that network latency due to geographical distance and not a prolonged Bigtable cold start. Once your web application, running on GKE, is in the same region as your Bigtable instance, the network latency between them will be significantly lower.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.