Thanks Marzia, Have GAE team thought about providing some "warm-up" url?
So if GAE see a load is increasing (and probably could predict a new request handler will be needed soon) then engine calls some URL specified in app.yaml (for example) and a request handler instance created and kept in cache for a while. So we do not waste time when a user request comes? I do not talk about 100% accuracy but some sort of pro-active warming would benefit. May be you could even disable calls to DB/memcache/etc so it is just modules initialization. -- Alex http://sharp-developer.net/ On Dec 12, 6:49 pm, Marzia Niccolai <ma...@google.com> wrote: > Hi Alex, > > We are definitely interested in offering Django 1.0 with App Engine in the > future. However, it seems likely that including Django 1.0 as the default > Django version with App Engine would need to be part of an api version > change, since such a change would likely brake existing apps. > > In terms of the high CPU warnings, we are generally working on a solution > that will lesson the affect of such warnings on applications, so we hope we > can address this soon not just for this case, but in general. > > As for the time concern, there isn't much right now that can be done. But > as your application increases in popularity, it's more likely people will > see an already warm interpreter and thus not have to wait for a new > initialization. > > -Marzia > > On Fri, Dec 12, 2008 at 6:14 AM, Sharp-Developer.Net < > > alexander.trakhime...@gmail.com> wrote: > > > Hi, > > > Any plans to update Django 0.96 to Django 1.0 ? > > > The 1.0 has been released on Sep 3 and still not there. > > > I use local version of Django 1.0 and it's OK but my concern is > > performance and CPU usage. > > > Whenever new instance of handler is created by GAE it takes some time > > and I guess CPU cycles. > > > I've noticed Django loading and appengine_django helper installation > > takes solid amount of time (~0.8 sec) and I guess CPU cycles. > > > See log extract from "main.py" : > > ==================================================== > > # 12-11 10:42AM 27.040 - Loading django helper... > > # 12-11 10:42AM 27.862 - Successfully loaded django helper > > ==================================================== > > > It does not affect my CPU quota but harm user expirience and make me > > nervous when checking logs in admin console :). > > > I assume if we load Django provided by GAE it will be pre-loaded and > > thus no CPU/time penalities for app. Is my assumption correct? > > > Would be really great if we could get the Django version 1.0 provided > > by default. > > > The latest reply on this is > >http://groups.google.com/group/google-appengine/msg/c3bb71cd63d8d32f > > > May be we should fill a feature request to speed it up? > > > P.S. I'm wonder what if Django could be provided pre-patched as an > > option? > > > P.P.S. I know - this is too specific request for general platform as > > GAE so would be happy to get any advises on speeding up "cold" > > requests. For example I already do not load Django if page content > > found in memcache. Still would prefer to have Django pre-loaded. May > > be by specifying this in app.yaml? > > -- > > Alex > > http:/sharp-developer.net/ > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
