StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>blackjack75,</p> <ul> <li>You're right, raising the pending latency to something like 10 seconds will help reduce the number of instances started.</li> </ul> <p>It looks like the long running requests tied up your instances. When this happens, app engine spins up new instances to handle the new requests, and of course instances cost money.</p> <ul> <li><a href="https://developers.google.com/appengine/docs/adminconsole/performancesettings" rel="nofollow">Lowering your min and max idle instances</a> to smaller numbers should also help.</li> </ul> <p>On your dashboard, you can look at your instance graph you to see how long the burst of instances was left idle after the request load was finished. You can look at your typical usage to help estimate a safe max. Lowering them can cause slowness when legitimate traffic needs to spin up a new instance, especially with bursty traffic, so you would want to adjust this to match your budget. For comparision, on a non-production appspot having the min and max set to 1 works fine.</p> <p>Besides that, <a href="https://developers.google.com/appengine/articles/managing-resources" rel="nofollow">general techniques</a> for reducing app engine resource usage will help. It sounds like you've gone through that already since your typical request time is low. Enabling concurrent requests could help here if your code will handle threads correctly (no globals, etc.) and your instances have enough free memory handle multiple requests.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload