I wrote a blog post about this before http://blog.ugorji.net/2011/09/objective-gripes-with-new-google-app.html
In thinking more, it seems like the following knobs should be sufficient to give us control over our budgets, and have graceful degradation of performance when things get high. - max-total-instances - max-idle-instance (which can be set to zero. So any unused instances should be shut down. Folks wanting always-on can set this to a higher value.) - min-pending-latency (this is the default value at which a new instance is started. If num-instances == max-total-instances, then allow the pending-latency to go up to either 15 or 30 seconds before returning a 503 Service Unavailable). This could allow Google the simplicity of a minimum set of knobs to start, while allowing us control our budget and degrade gracefully. -- 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/-/0gedf-B1-u4J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
