Hello,
The first request made after deployment usually takes longer than subsequent requests as well as the first request when an application has not been serving traffic for a while since it will be a loading request <https://cloud.google.com/appengine/docs/standard/java/configuring-warmup-requests>. As you mentioned, using warmup requests is a way to reduce or avoid this latency. However, please note that warmup requests won’t work in every case <https://cloud.google.com/appengine/docs/standard/java/configuring-warmup-requests>. Now, if you have noticed that even after that initial request, while your application is serving requests normally it’s still taking a while, I would recommend you to increase the number of minimum idle instances so there will be an instance ready to handle requests which should reduce the latency while autoscaling. However, if you believe the delay is unusual and you would like to get more detailed information, you may open a support ticket <https://cloud.google.com/support#tab2> where your application would be analyzed in order to get more information about what could be causing this delay. Please note that if you are during a free trial period, you are able to open a support ticket using the free trial support <https://support.google.com/cloud/contact/free_trial_support>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6867a4c0-e4d1-4832-ad3a-5349e7eca474%40googlegroups.com.
