You might be interested in this issue : http://code.google.com/p/googleappengine/issues/detail?id=2456
On 10 jan, 14:34, Jorge <[email protected]> wrote: > It's been some discussion about this topic. You may want to seek posts > with words "keep warm" or "cold start", for instance. See also the > "Tragedy of the Commons, and Cold Starts" post in the Google Aps Forum > > http://groups.google.com/group/google-appengine/browse_thread/thread/... > > Jorge Gonzalez > > On Jan 9, 3:16 pm, Locke <[email protected]> wrote: > > > > > In my testing, apps which are hit every 2 minutes need to "boot" every > > time (costing beacoup CPU cycles), whereas apps hit every 1 minute > > stay loaded. > > > This limit seems to have changed over time. When I started using > > appengine several months ago, it would wait ten minutes before > > subjecting you to the unload/reload penalty. > > > I would gladly send google a stick of RAM in the mail if they would > > just keep my app going! ;-) > > > On Jan 9, 8:16 am, Yossi <[email protected]> wrote: > > > > Hi, > > > > I've noticed that the same request that takes in average 2 seconds > > > could take more then 20 seconds after around 10 minutes that the > > > application is idle (no requests are received). I assume that after > > > ~10 minutes of no requests, the GAE shuts-down the instance. > > > Is there an official information about this period of time? Is there a > > > way to extend this period of time (besides writing a cron job that > > > runs every minute)? > > > > Thanks. > > > > Yossi
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
