Why in Google App Engine Always 11 secs of Latency coming only for the first requests?

[Sudhanshu Gaur]

Hii, actually I am making just a sample NodeJs app in flexible environment with just one route and nothing else in the code. But when I am trying to call this API from my android app, I am getting latency of 40 seconds(when I am using my domain url) and 11 secs(when I am using appspot.domain url).

Now in order to debug this I checked in trace api where there total latency was in milisecs, also when I checked in Logs I found that the Logs which I am printing when insideAPI code gets executed was after 40 secs,.

Can you please help me where these 40 secs are getting wasted?

Nothing is working for me Please Help.

[Sudhanshu Gaur]

I found that

This can be a caused when your application is still booting up or warming up instances to serve the request and can be called as loading latency. To avoid such scenarios you can implement health check handler like readiness check so that your application will only receive traffic when its ready

That's why I checked in my Logs that readiness check is performed sometimes around 1 sec and sometimes around 200 ms







Can anyone please tell me is there anything wrong in warming up my instances because I don't think cold boot time is causing this problem.

Please Help

[Dan S (Cloud Platform Support)]

Hello,

It seems that you have reported this issue in the Issue Tracker:

https://issuetracker.google.com/issues/113672643

therefore, I'll be closing this issue in this channel an I will assist you through the mentioned link.

[Marc Samet]

remove me immediately from this group

On Sep 2, 2018, at 1:51 PM, Sudhanshu Gaur <sudhan...@gmail.com> wrote:

I found that

This can be a caused when your application is still booting up or warming up instances to serve the request and can be called as loading latency. To avoid such scenarios you can implement health check handler like readiness check so that your application will only receive traffic when its ready

That's why I checked in my Logs that readiness check is performed sometimes around 1 sec and sometimes around 200 ms




<google_cloud_logging.png>




Can anyone please tell me is there anything wrong in warming up my instances because I don't think cold boot time is causing this problem.

Please Help

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@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/bf7fdce9-8079-4227-a969-b88c555febb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<google_cloud_logging.png>

Marc K. Samet, Ph.D.

[Steren Giannini]

Dan, it seems that the issue is not public. Would you mind making it public or keep the conversation in the public forum?

--

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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@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/82c7b4a1-98ac-4496-8f50-ea7d2237ddd3%40googlegroups.com.

[Sudhanshu Gaur]

Thanks a lot for assisting @Steren, waiting for the solution.

[Dan S (Cloud Platform Support)]

Hi Steven,

I'm handling the case in private because I am investigating the case with the customer. As soon as we find a solution I will remove private information and set the case as public again.

Cheers

On Wednesday, September 5, 2018 at 5:08:09 PM UTC-4, Steren Giannini wrote:

Dan, it seems that the issue is not public. Would you mind making it public or keep the conversation in the public forum?

On Mon, Sep 3, 2018, 08:08 'Dan S (Cloud Platform Support)' via Google App Engine <google-appengine@googlegroups.com> wrote:

Hello,

It seems that you have reported this issue in the Issue Tracker:

https://issuetracker.google.com/issues/113672643

therefore, I'll be closing this issue in this channel an I will assist you through the mentioned link.

On Sunday, September 2, 2018 at 1:51:12 PM UTC-4, Sudhanshu Gaur wrote:

I found that

This can be a caused when your application is still booting up or warming up instances to serve the request and can be called as loading latency. To avoid such scenarios you can implement health check handler like readiness check so that your application will only receive traffic when its ready

That's why I checked in my Logs that readiness check is performed sometimes around 1 sec and sometimes around 200 ms







Can anyone please tell me is there anything wrong in warming up my instances because I don't think cold boot time is causing this problem.

Please Help

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.

[Suvodeep Pyne]

Hi Dan

Has the issue been resolved yet? I am seeing large latencies in my Flex instance and was wondering if this thread could help. As Steren mentioned, it would be great to have the issue public.

@Sudhanshu, would love to hear an update.

Regards

On Thursday, September 6, 2018 at 8:13:51 PM UTC+5:30, Dan S (Cloud Platform Support) wrote:

Hi Steven,

I'm handling the case in private because I am investigating the case with the customer. As soon as we find a solution I will remove private information and set the case as public again.

Cheers

On Wednesday, September 5, 2018 at 5:08:09 PM UTC-4, Steren Giannini wrote:

Dan, it seems that the issue is not public. Would you mind making it public or keep the conversation in the public forum?

On Mon, Sep 3, 2018, 08:08 'Dan S (Cloud Platform Support)' via Google App Engine <google-a...@googlegroups.com> wrote:

Hello,

It seems that you have reported this issue in the Issue Tracker:

https://issuetracker.google.com/issues/113672643

therefore, I'll be closing this issue in this channel an I will assist you through the mentioned link.

On Sunday, September 2, 2018 at 1:51:12 PM UTC-4, Sudhanshu Gaur wrote:

I found that

This can be a caused when your application is still booting up or warming up instances to serve the request and can be called as loading latency. To avoid such scenarios you can implement health check handler like readiness check so that your application will only receive traffic when its ready

That's why I checked in my Logs that readiness check is performed sometimes around 1 sec and sometimes around 200 ms







Can anyone please tell me is there anything wrong in warming up my instances because I don't think cold boot time is causing this problem.

Please Help

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.

[Katayoon (Cloud Platform Support)]

Hi Suvodeep,

The original poster had posted the issue in this Stack Overflow thread and you may take a look at the answers provided in the thread, however Issue 113672643 will be visible in public after removing customer's private data. I have asked the Cloud Privacy team to remove the sensitive data and as soon as they remove it, I'll change the visibility as public.

I should also note that Google Groups are reserved for general questions on Google Cloud Platform-end products and not for reporting issues. For reporting issues and feature request, I recommend to create a ticket in the Issue Tracker so that we would be able to handle it efficiently.

[Nico Verwer]

In the stackoverflow thread mentioned above, the conclusion is:

The issue is resolved now, it was happening because of network service provider which is Bharti Airtel, their DNS lookup was taking the time to resolve the hostname. After explicitly using alternative DNS like Google 8.8.8.8 the issue got completely resolved. Maybe it's a compatibility issue of Airtel with Google Cloud.

I thought it might be useful to mention that for those who experience latencies and come to this page.

[Sudhanshu Gaur]

Is your issue resolved now?