[google-appengine] Re: Policy for instance startup

2010-12-03 Thread Tomas Alaeus
I hoped that Warmup Requests could be used to remedy the situation (at least from a users perspective). Unfortunally, it does not help anything. Warmup requests seems to be inactive (or not react) when there are less than 10 instances active for my live app. The warm up requests starts to work

[google-appengine] Re: Policy for instance startup

2010-11-26 Thread Tomas Alaeus
This problem doesn't seem to happen on the staging server (doesn't have billing enabled), but I maybe haven't stressed it enough. Another application I have for testing purposes seem to be affected by it too, and it doesn't have billing enabled either. That application seems to want at least 4

[google-appengine] Re: Policy for instance startup

2010-11-24 Thread nickmilon
While waiting from a Googler to give us some light on this may be you do your stress tests in the staging server ? (just an other version will do as staging server) Also I remember people from App Engine team stating here that the best performance comes when load comes in a natural matter. Still

[google-appengine] Re: Policy for instance startup

2010-11-23 Thread nickmilon
Not been a Googler can't help much with this. Having said that, I suspect there is a kind of build in algorithm that does some kind of application profiling taking into acount QPS, response times, and other parameters which adjusts instance life time, number of instances to start etc.. This could

[google-appengine] Re: Policy for instance startup

2010-11-23 Thread Tomas Alaeus
Probably. With some more thinking I got to this conclusion: At first, an application can utilize up to 30 instances. After having used all those instances for a few minutes, and it still isn't enough, GAE will increase the maximum number of available instances to 40, and then to 50 etc. Every