4 ms·
(GCP Gopher here) If you can run within the standard environment, I'd suggest you do (but you should check pricing, etc to see if it suits). Especially if you
by chrisbroadfoot 8y ago
(GCP Gopher here)
If you can run within the standard environment, I'd suggest you do (but you should check pricing, etc to see if it suits). Especially if you want 0-1 scaling.
I migrated golang.org from standard to flexible a couple weeks ago, primarily because of increased control over the runtime (custom Docker image) and increased instance sizes (configurable memory, CPU past the App Engine limits, which caps out at 2 GB). See https://golang.org/issues/27205 https://golang.org/issues/27205 if you want to read more.
- iamgopal 8y agoDo you have blog post with data, number of instances etc previously and now ?
- chrisbroadfoot 8y agoI don't, sorry. While the app was unhealthy, it was spinning up dozens of instances. While it was healthy (on standard), I recall it ran on less than a handful of instances. It currently runs on two fat flexible instances (GCE VM), but could easily run on one. We only run on two for some redundancy. I've measured throughput of ~thousands of requests per second on a F4_1G on apps I've worked on previously. They were CPU-constrained, but not doing very much (JSON serialization). The new runtime might be even better, since GOMAXPROCS is no longer 1. correction to my post above: 1 GB is the max memory for standard: https://cloud.google.com/appengine/docs/standard/#instance_classes https://cloud.google.com/appengine/docs/standard/#instance_c...