I spoke too soon. Some time after posting this, testing revealed more
problems. Upon diagnosis, it appears that GAE is too aggressive at
spinning up new instances even when the auto/auto setting is used,
although the behavior is less reproducible than when a min of 1 is set.
The only fix I
PS. I once again encountered evidence that appstats is causing requests to
fire even when I'm not actively using the management console, which is very
weird. I've turned off appstats because I didn't really find it all that
useful anyway (and because it causes the dev server not to start when
So, this behavior is completely reproducible.
1) Shut down all instances.
2) Set min instances to 1 (leave all other sliders at default values).
3) Save settings and wait for instance to spin up.
4) Issue one GET request from browser to a specific API endpoint. This is
an API call so it is not
The above post notwithstanding, the original problem I was having - which
caused me to try to set min instances to 1 to begin with - seems to have
gone away. I know this is probably going to fall into the PEBCAK bucket,
but I really don't think I did anything in particular to cause the
Hi Kristopher,
On Wed, Aug 1, 2012 at 11:18 AM, Kristopher Giesing
kris.gies...@gmail.com wrote:
I've been working for some time on an app I plan to deploy. Over the
development period I have done testing on the QA instance of my app (which
is a separate app ID from the one I'll use in
Hi Takashi,
Thanks for the prompt response. Info below...
On Tuesday, July 31, 2012 8:30:58 PM UTC-7, Takashi Matsuo (Google) wrote:
Hi Kristopher,
Where are you accessing your app from? Ping result is just for our
frontend facilities, so it doesn't reflect the real network latency of
