[google-appengine] Re: Sporadic server error since March 1 (Python)

In this case cold boot can not be made any faster by making code simpler. It's just a simple db (db has less than 10 rows) lookup and response. If that is something that F1 instance is not able to serve from cold boot - it is useless. I would also like to add that for such simple queries

[google-appengine] Re: Sporadic server error since March 1 (Python)

Thank you for sharing your experience with us. You are saying that your machine workload does not match the machine type requirement and that you didn’t expect to upgrade to a class F2 instance. I will try to help. There are some ways to mitigate this error message [1] such as: 1.

[google-appengine] Re: Sporadic server error since March 1 (Python)

I had similar problem few months ago when suddenly extra instances were created for another app that wasn't receiving any extra traffic. And I am not the only one who experienced that. Something is obviously happening on the google side, it's ridiculous that I can't serve a simple request with

[google-appengine] Re: Sporadic server error since March 1 (Python)

Glad to hear that switching to a F2 instance class fixed the issue. It’s hard to say whether the issue was caused by a lack of resources even after looking at the log you provided. Which is why I would recommend you to contact GCP support If this issue

[google-appengine] Re: Sporadic server error since March 1 (Python)

Many thanks for your tips! The trace is not available for failed request, for all other it is. I haven't pasted log earlier, perhaps I should, because (in my opinion) it isn't showing anything. Here it is (attached). Meanwhile, I have switched to instance class F2 and so far the problem did

[google-appengine] Re: Sporadic server error since March 1 (Python)

The error you’re sharing could be caused by many different reasons. Please check Logs Viewer in Google Cloud, as shown in this Using Logs Viewer documentation, and share what you see