Why all of a sudden my instance initialization taking so long and causing 429 rate exceeded for single request

[PPG Apps]

I have an app that has been running for a long time.  All of a sudden a few days ago, it is randomly (but often) taking over 10 seconds to start up and returning 429's.  It is just a basic python webapp2 application servicing a few DB lookups.  But now all of a sudden it takes forever to start up even when it isn't doing a DB lookup. There is literally a single Android app user and a single web user. It takes more than 10 seconds to start up and serve a basic html page?

 I'm using free quotas.  I currently have it set as:

instance_class: F1
automatic_scaling:
  max_idle_instances: 1
  max_instances: 1

This worked fine for a long time. The load on it is actually less now then it was when it was actually working properly. The quota page says I'm nowhere near any quotas.  How can I determine what changed? Did google change? Some setting needs tweaking?

How can sometime it take leas than two seconds to instantiate and some time more than twelve seconds?  How can sometime it take ten seconds and abort with 429 while other times it take twelve seconds and still service the request?

Any help in diagnosing appreciated. 

[Elliott (Cloud Platform Support)]

Hello,

Google Groups is meant for general discussion of Google Platform products. To report an issue, please use Google Issue tracker where we may make the request private to share project information.

[PPG Apps]

Ok sorry. done. 157136105