With regarding to the experienced logging message stating: "After handling this request, the process that handled this request reached the maximum number of requests that may be handled in a single process' lifetime, and exited normally."
See my comment in this thread: https://groups.google.com/forum/?hl=en#!topic/google-appengine/fF8DO8iQmqw - Fredrik On Monday, August 8, 2016 at 12:49:41 PM UTC+2, Iliya Novikov wrote: > > Thanks for your replies, Adam and Marcel, > > After a few days of experimenting with settings for the automatic scaling > all of a sudden the warm-up requests started to work for us. This is > something I can't really explain. My guess is that this has changed after I > set up some non-zero "min-idle-instances" (previously it always was 0). The > most interesting is that after I noticed this change I rolled back all the > settings to as they were and the warm-up requests are still coming. So > ultimately the system works well with exactly the same settings we always > had. This is a total mistery, but the problem seems to be solved. > > Thank you, > Iliya. > > On Monday, August 1, 2016 at 5:40:43 PM UTC+2, Marcel Manz wrote: >> >> Hi >> >> I second Adam's suggestion to use manual scaling in order to not run into >> any latency issues. We're running on manual scaling for several years now >> and this proved the only scaling method guaranteeing no latency issues. >> >> Eg. when we tried with basic-scaling, we discovered that: >> >> 1. There is no min-instances parameter. In worst case app engine will >> scale down to 1 instance, but if you encouter a sudden traffic spike there >> won't be any prewarmed, unused instances. We would like to see here a >> config option where min-instances can be configured on basic-scaling. >> >> 2. Even though we have warmup requests configured, some requests still >> went to newly created instances, thus adding latency for the time it takes >> to serve the first request. >> >> As our application has to deliver consistent performance, we chose >> manual-scaling instead. >> >> @Adam, regarding setNumInstances() >> <https://cloud.google.com/appengine/docs/java/javadoc/com/google/appengine/api/modules/ModulesService#setNumInstances-java.lang.String-java.lang.String-long-> >> >> method: Is there some kind of method to programmatically retrieve the >> active instances value, as like the active green line as shown in the >> dashboard when 'Instances' is selected? Or similar the current latency >> value when 'Latency' is selected? >> >> For our application it seems a better fit to use manual-scaling, but use >> a custom load balancer control function that will use setNumInstances() to >> scale the instances depending on load. >> >> Thanks & Regards >> Marcel >> >> >> -- 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 [email protected]. To post to this group, send email to [email protected]. 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/399ae088-768f-4f80-be9f-d9424d092820%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
