Heyo, On Tue, Mar 10, 2009 at 7:16 PM, cz <czer...@gmail.com> wrote: > Actually, that is normal behavior. This has been discussed in previous > threads. > GAE seems to aggressively purge it's app cache, average app lifetime > appears to be under 2 seconds. Appengine-patch may be marginally > faster but both require Django1.x to be imported via zipimport, which > is pretty expensive. > Our app also exhibits this problem due to fairly low traffic, but > there's not much that can be done as far as I can tell. Our app's > dynamic pages contain lots of images also served via GAE, and since > the browser can make many requests at once to load these, the app can > be started up on several sever instances (probably due to load > balancing) to deliver all the images. This can add up to a huge amount > of CPU usage for just one page. > Basically, the more traffic your app gets the faster it will be. > Some people have suggested using a process somewhere to automatically > make requests once per second or so to keep apps in the cache. But > this is surely frowned upon by Google.
Indeed, we are aware of this issue for some applications with certain load characteristics. We're taking steps to improve app caching to maximize instance lifetimes when it makes sense. Thanks for reporting all of your experiences with this behavior! -Brett --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
