I am very interested in this also. There are features of the Patch I'd really like to use, but I keep hearing that startup times (for new machine instantiations, which we all know happens quite frequently) are significantly higher than bundled Django, which in turn are significantly higher than using just web_app.
Can anyone quantify this? On Aug 15, 1:53 am, Waldemar Kornewald <wkornew...@gmail.com> wrote: > Hi Andy, > > On Aug 14, 7:05 pm, Andy <a...@robotlovesyou.com> wrote: > > > I've not compared appengine-patch and google-app-engine-django for > > performance but when using google-app-engine-django r86 (which used > > django 1.0 via zipimport) I was getting a high-cpu warning for every > > second or third page load and for each of these pages the logs showed > > that zipimport wa re-loading django. When I moved across to google-app- > > engine-django r90, which uses the built in django 1.0 libraries this > > issue went away and my cpu usage and page load times dropped > > significantly. > > How did you check this? Did you go to the logs and then select > "Minimum severity: Requests only"? The zipimporter always adds INFO > logging messages, so you'll notice Django loads. Without zipimport you > have to go to the request level to see Django loads. I'm pretty sure > you'll find some requests with unusually high CPU and long response > times. > > I'm really interested in some real-world data on whether there is a > difference between integrated and external libraries - this is not an > aep vs helper battle. > > Bye, > Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
