I went back to my logs..I was ignoring a certain request previously, so that's why I was missing my 'cold starts'! For some reason, one of my particular requests seems to get all my cold starts. However, the request and cpu times I'm seeing for these cold starts are quite different from what Jason is reporting. Typically they range from 1000-1600ms and 1900-2100 ms-cpu.
On Mar 11, 8:13 am, Jarek Zgoda <jarek.zg...@gmail.com> wrote: > I'm seeing the same behaviour but I do not use Django (Werkzeug + > Jinja2). While this combo seems lighter (in terms of CPU usage), my > app becomes "cold" each 2-3 seconds and request takes > 1200ms CPU to > be served, with Jinja2 Environment creation taking most of CPU > resources. I tried to optimize this process by caching what can be > cached but got little to none improvement as not much can be cached > here (only loader and templates). > > On 10 Mar, 18:22, 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 -~----------~----~----~----~------~----~------~--~---
