At the moment I've found that the best way to keep it capped to 1 instance is to ensure that the 1 instance you have does not die. The problem is when there are 0 instances running, and 2 quick requests come in, the scheduler will startup 2 instances to handle both requests. So what I did was to add a heartbeat cron job to send in a request to a servlet that does nothing, once per minute. This seems to work great, keeping that one instance going. The deployment was made 8 hours ago, and there has only been 1 instance since then.
<https://lh3.googleusercontent.com/-iV0d-wg5j3U/TmOo3IyHeQI/AAAAAAAAAsA/4eeCiku-iyY/snapshot6.png><https://lh3.googleusercontent.com/-gppWVC7FQLw/TmOo4f9-YSI/AAAAAAAAAsE/IJzHiS7oJYc/snapshot7.png> -- 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/-/Ts-Sy0yxQLgJ. 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.
