That's an excellent point. Can I assume that (if) I ever reach the billing limit, the cache will last longer than 2 seconds?
On Mar 11, 11:00 am, peterh <peter.hau...@gmail.com> wrote: > On Mar 11, 12:28 pm, johnP <j...@thinkwave.com> wrote: > > > I've been tracking (and seeing) this for a while already. Besides the > > latency that occurs each time Django gets re-zipimported, what is > > concerning is the thought of paying for CPUs to constantly reload the > > cache. My app's not live yet - so there is some time before this > > becomes a $$$ problem for me, but... > > But how can you reach your billing limit if the issue is that you get > low traffic in the first place? other than that, I agree, it would be > great if this 2-sec limit was increased. > > > I remain forever hopeful that it will be solved by then. :) > > > On Mar 11, 4:26 am, Antonin Hildebrand <antonin.hildebr...@gmail.com> > > wrote: > > > > I can also confirm this behavior with my app, recycling takes place > > > after about 2 seconds of inactivity. I also guess, that this recycling > > > timeout had to be lowered by GAE team during last week, because I had > > > running and working application on appspot. I did no updates to it and > > > the app did break because of this change. > > > > On Mar 10, 6:22 pm, Jason C <jason.a.coll...@gmail.com> wrote: > > > > > We have a new application that receives _very_ little load. So little, > > > > in fact, that each request spins up a new application instance. We are > > > > using Django trunk and the import overhead is high. All of this yields > > > > a long request (e.g., 8802ms) using a lot of CPU (e.g., 3247ms-cpu). > > > > > With very little load, it makes sense that instances are recycled. On > > > > that assumption, we've started applying some primer load against a > > > > couple of uris in an attempt to keep some instances hot. We're > > > > applying around 1 request/second across 2 uris. > > > > > When we hit a hot instance, we get blazing speed (e.g., url_1: 73ms > > > > 91ms-cpu, url_2: 368ms 615ms-cpu - these values are pulled from the > > > > App Engine console Logs tool and I'm not completely sure if this > > > > represents Runtime, or combined Runtime/API - I believe the latter). > > > > > Under this 1 request/second load, we are still seeing lots of instance > > > > startup - even after 40-50 minutes of sustained load. Subjectively, > > > > the instance startups seem to come in bursts, though we've done no > > > > formal analysis around this. > > > > > Does anyone else see this behavior? It _really_ kills our application > > > > performance - so much so, that we're considering moving away from > > > > Django in an effort to minimize the start-up pain. > > > > > Any info or war stories would be appreciated. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
