We are considering implementing our own automatic scaling policy by periodically monitoring our service and calling the SetNumModules() API that App Engine provides. We want to work around the bug that when you deploy to an automatically scaled Flexible Environment service, the current policy switches your production load on to your minimum number of instances, rather than scaling up the new version to match the old version (issue filed):
https://code.google.com/p/googleappengine/issues/detail?id=12936 Before we embark on this bug workaround adventure: has anyone successfully written their own automatic scaling policy, for any reason? Was it easy or hard? Are there any bugs for us to be aware of? Thanks! -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/ae21b89d-8f8e-496c-922d-5b43cff28a87%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
