4 Instance spinning in 4 secs

[Rajesh Gupta]

Hello 

Following is the traffic to our website.  

You can see suddenly, there are new four instances ('i' in the orange color denotes log.warning).  I do log.warning in my context listener.  Between 23:32 & 23:36, ie 4 secs, there are new four instances.  The traffic could have well served with the normal instance.  Each of the instance spinning and serving is taking approx 22 sec.  

This is a very bad experience to our users.

Please suggest the recommended correct settings for low traffic website, so that instance spinning is not taking place.

23:54:14.017GET200203 B132 msGooglebot 2/robots.txt

23:54:12.571GET200203 B1.2 sGooglebot 2/robots.txt

23:36:08.111POST20031.12 KB23.3 sChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.listProducts

23:35:51.633POST200291 B22.6 sChrome 55/_ah/spi/com.veersoft.services.api.ReportAPI.viewLedgerTransaction

23:34:09.281POST20051.89 KB19.1 sChrome 55/_ah/spi/com.veersoft.services.api.ReportAPI.viewLedgerTransaction

23:33:10.557POST2003.49 KB1 sChrome 55/_ah/spi/com.veersoft.services.api.ReportAPI.viewLedgerTransaction

23:33:06.428POST2001.46 KB246 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.listBankCashAccounts

23:32:40.392POST20031.12 KB463 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.listProducts

23:32:11.464POST2008.87 KB26.5 sChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction

23:31:56.158POST200644 B594 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction

23:31:09.541POST2008.87 KB707 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction

23:30:34.928POST2007.83 KB807 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction

23:30:11.573POST20027.9 KB672 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.listCustomer

23:29:55.646POST2005.01 KB692 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction

23:29:18.924POST20027.9 KB928 msChrome 55/_ah/spi/com.veersoft.services.api.MastersApiV3.listCustomer

--

Regards,

Rajesh

www.VeersoftSolutions.com

www.GainERP.com

Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and Mobile

[Rajesh Gupta]

Sorry, in 4 minutes (not 4 sec) there are 4 new instances.  You can see that betwee 23:32 & 23:36.

There are only 6-7 requests during that time.

[Nick (Cloud Platform Support)]

Hey Rajesh,

The scaling behaviour on your app is highly dependent on the contents of your app.yaml / appengine-web.xml file. Could you post that?

Also, it would be good to get a larger time-window selection of logs in text format (rather than screenshot) along with a screenshot of the instance numbers graph covering the same time period. This would be very helpful in reasoning about what is happening here.

If you have any further questions, feel free to send them along with your reply and I'll be glad to assist in answering them. 

Cheers,

Nick
Cloud Platform Community Support  

On Sunday, December 25, 2016 at 9:56:07 PM UTC-5, Rajesh Gupta wrote:

Sorry, in 4 minutes (not 4 sec) there are 4 new instances.  You can see that betwee 23:32 & 23:36.

There are only 6-7 requests during that time.

[Rajesh Gupta]

Hello Nick,

Is there a way to get the txt of the log files.  I don't see any options to export the logs for the given time to a txt file.

I cannot pass on the text logs to the group, as url's contain some information.  I will open a production case.  

 

Regards,

Rajesh

www.VeersoftSolutions.com

www.GainERP.com

Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and Mobile

--
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.
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/2cc43cd5-7ef2-4e1c-9d54-819325eec656%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nicholas (Google Cloud Support)]

To get logs for a specific GAE service, you can use one of the following:

• Selecting the text of the logs in the browser when viewing the Logging window in the Developers Console.  With most modern browsers, it's possible for web site designers to control how content is copied and pasted despite how it may be rendered on the page.  Thus, some page components that seem as though they won't look right when pasted elsewhere in plain text can actually look readable.
  
• Cloud SDK in the terminal with app logs read.  The output of such commands is generally formatted to be read in monospace, plain text window and are therefore suitable for plain text exchanges.
  

     gcloud app logs read --level=debug --service=<your-app-service> --version=<your-app-service-version>

• Create an Export into a sink like Cloud Storage so that you could then share the logs as files in an email
  

These are generally very useful ways to troubleshoot as it makes it easier search key terms from logs in forums such as Google, Stack Overflow or this Google Group.  I hope the above is helpful.

[Nick (Cloud Platform Support)]

One thing I'd add to the above excellent comment by Nicholas G:

There's currently a beta feature in the gcloud tool which can read app logs and show any info, warning, error, etc. logs from within the requests, while the gcloud app logs read won't show this information:

gcloud beta logging read

As to your last comment, Rajesh, yes I'd say that gathering logs like this will contain information you probably don't want to share with the public, so you would want to either email it to us directly or open a Public Issue Tracker report with the label "Restrict-View-EditIssue".

Cheers,

Nick
Cloud Platform Community Support

[Nick (Cloud Platform Support)]

... and as a last bit of additional information, if you use gcloud beta logging read, be sure you read the help document for that command (gcloud beta logging read --help) and pay special attention to the need to use filters to specify the resource you want to target.