I had same issue with always-on feature. It had 3 resident instances up with no traffic and a new request came in and it spun up another instance to serve the new requests while the resident instances were still idle. My app only gets heavy traffic on certain days - so not sure if the scheduler thought it needed to get ready for next spike or what.
I have since changed the max idle instances from automatic to a number that is more realistic during those days. That has helped to keep the number of extra instances down. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/bYKpOh0rVlkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
