Our app uses *ah-builtin-python-module* for backup. Backups are configured to execute quickly. We noticed that there are several (6) idle instances allocated to *ah-builtin-python-module*. We believe that the high instance count is caused by automatic scaling. The algorithm expects the next spike of activity caused by regular backup jobs and leaves some instances idle to reduce initial request latency. In the case of backups we don't really care about request latency.
The question is: can we configure *ah-builtin-python-module *to spin down instances quickly like we do with the default service? Backup queue config: - name: backup mode: push rate: 100/s bucket_size: 20 target: ah-builtin-python-bundle Default service config: automatic_scaling: max_concurrent_requests: 32 max_idle_instances: 1 min_idle_instances: 0 max_pending_latency: "100ms" min_pending_latency: "30ms" Ivan -- 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/847126bd-f7a6-4675-aa53-f6e5e573d403%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
