3 ms·
There is no solution in the admin settings, nor according to their enterprise support. It is plain old tough luck. The vast majority of our traffic is from de
by rogerbinns 13y ago
There is no solution in the admin settings, nor according to their enterprise support. It is plain old tough luck.
The vast majority of our traffic is from devices that retry later if anything goes wrong. It is analytics information and hence there is no human affected by it.
Despite having identical settings and code across a number of appengine apps, we see variance in the number of instances they decide to run (eg they will start 4 at once even though only 1 is needed for the load).
At one point they were starting hundreds of instances due to some of our aggressive inter-app traffic (thundering herd problem). Things would have worked fine if we could limit the number of instances, but tough luck there. It required considerable engineering and tuning to make the problem go away that would have trivially been solved (in the short/medium term) by limiting instance numbers.
- StavrosK 13y agoHmm, you must be talking about something else, but there's a "min/max instances" slider in the console. I have set it to 1 for many of my apps, and they never go over 1 (or at least I don't get billed for it).
- rogerbinns 13y agoI only have that slider for idle instances, which you aren't charged for. It is limiting the active instances I am talking about.
- StavrosK 13y agoYeah, you're right. It has just never spawned more active instances than that slider is set to, for me.
- rogerbinns 13y agoAll it takes is some unwanted traffic and appengine will be happy to start an unlimited number of instances for you.