That totally sucks. I can understand that it takes up more resources to have an app always loaded in an instance but when minimum instances is set, then it should mean that the app is kept in memory. If what you write is true (and I guess it is since nobody from Google has objected to it) then Google is not fulfilling what they themselves claim: "Because App Engine keeps idle instances in reserve, it is unlikely that requests will enter the pending queue except in exceptionally high load spikes." http://code.google.com/appengine/docs/adminconsole/performancesettings.html
On Thursday, March 8, 2012 10:10:03 PM UTC+1, Mark Rathwell wrote: > > Just wanted to follow up on this: > > Idle instances set to 1: 7 of 10 requests were loading requests (20-30 > seconds) > Idle instances set to 2: 3 of 9 requests were loading requests (and > cost was about 4 times as much) > > This is a test app, with no other traffic, no new versions uploaded, > etc., and these requests were about once a day for the last few weeks. > I'm giving up on finding a setting that will mimic always on for low > traffic apps, and just setting up a cron job to ping the apps > regularly. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/ly0xBCd9rVkJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
