You could increase your pending latency settings to the maximum allowed, in
order to try to have your app wait as long as possible for an existing app
instance to serve a web request. I use:
<automatic-scaling>
<min-idle-instances>1</min-idle-instances>
<max-idle-instances>automatic</max-idle-instances>
<min-pending-latency>15.0s</min-pending-latency>
<max-pending-latency>automatic</max-pending-latency>
[...]
</automatic-scaling>
to implement this, but I still get web requests being directed to a new app
instance which has just been launched and therefore is not ready to serve
immediately.
On Friday, 10 January 2014 06:23:09 UTC, aswath wrote:
>
> Hello,
>
> The user facing requests are going into the instance startup and getting
> served. Any settings recommended recently for avoiding this.
>
> My settings are
>
> instance_class: F2
>
> automatic_scaling:
> min_idle_instances: 1
>
> max_idle_instances: 1
> min_pending_latency: 5.8s
>
> max_pending_latency: 5.8s
>
>
> -Aswath
> www.accountingguru.net.
>
--
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
