Thanks for the reply. It seems like the VM health check is contribution to the high ratio of 502 server errors. I've change the liveness_check and readiness_check in the yaml file and it appears to have improved the GAE stability. I will run a few stress tests and see the 502 error comes back.
On Tuesday, September 26, 2017 at 7:46:36 PM UTC-7, Kenworth (Google Cloud Platform) wrote: > > Latency can be caused by a number of things - geography, startup time, > size of payload, etc. You can visit this blog on How to Troubleshoot > Latency in your App Engine Application > <https://cloudplatform.googleblog.com/2015/08/How-to-Troubleshoot-Latency-in-Your-App-Engine-Application.html> > and > hopefully might help you isolate the latency problem. > > It is also helpful to observe how long request takes to respond through > Stackdriver > Trace <https://cloud.google.com/trace/docs/>. If this is not possible > because most of the requests timeout, one should try to make split up or > defer the work being done to respond to the request. > > If you are still affected after trying the above, I recommend you post on > StackOverflow > <https://stackoverflow.com/questions/tagged/google-app-engine> which we > also monitor. You'll be in touch with a much larger user-base of people who > are going to help you, in a format which is designed for that purpose. > Check out our community support page for the list of tags > <https://cloud.google.com/support/docs/stackexchange> we monitor. > -- 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/fd67cd2a-0a07-4b66-a1c1-a6216c472be9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
