Google App Engine何时启动或停止实例？

Question

We have an App Engine app that handles an average .5 requests per second, and seemingly all those requests can be handled by the same instance running a Go app as the main version.

However, sometimes App Engine kicks off a second instance (and sometimes even a third one), that doesn't seem to do anything past handling one or two requests. Here's an example.

Shutting down that instance manually doesn't seem to cause any harm, so my question is, why does App Engine not kill the instance after it did not get any requests for a while? (The above example had four requests in the past hour, often the requests/age ratio gets even lower).

Update:

A similar situation is when an instance is started on a different version. App Engine only seems to kill the instance after hours of not getting any requests.

Under Application Settings → Performance,

• Idle Instances is set to Automatic – 20
• Pending Latency is set to 150ms – 250ms

Answer 1

I wish I knew what controls if/when it kills idle instances, but I can't see any documentation of it.

To avoid excess instances starting, I think the main thing you can do here is increase the pending latency:

The Pending Latency slider controls how long requests spend in the pending queue before being served by an Instance of the default version of your application. If the minimum pending latency is high App Engine will allow requests to wait rather than start new Instances to process them. This can reduce the number of instance hours your application uses, but can result in more user-visible latency.

Even if you only average 4 requests/hour, if you happen to get two closely spaced I suppose it's possible it would start a new instance.

You can also see some small amount of information in the logs about why it started a new instance.