I see this too.. If i simply extract the django 1.0.2 into source folder and upload the app, it gets ridiculously fast.. ~2000ms -> ~84ms..
Google should host django 1.0 in a different path on web servers and give some configurable way either in app.yaml or in code. so we dont have to upload it along with our app. -Sarath. On Feb 14, 9:07 pm, Ross Light <[email protected]> wrote: > I'm thinking now that that's probably the case. After researching the docs, > it would seem as though the Engine distributes the load over different web > servers, which would cause the cache to cease to be. I'd still like to know > for sure, because it is rather annoying to have a lot of 2000ms requests. > > On Sat, Feb 14, 2009 at 3:11 PM, captainslim <[email protected]> wrote: > > > On Feb 1, 2:02 pm, Ross <[email protected]> wrote: > > > I'm suffering from this problem, too. I'm using the Django Google App > > > Engine helper and it seems to be reloading the zip file for every > > > request. > > > Could it be that Google App Engine is caching apps for a very short > > length of time for low-use apps? I find that if I make a bunch of > > requests to my app in rapid succession, then I don't get the high CPU > > warning for requests after the first. If I allow a few seconds between > > requests, however, I see the warning about zipimporter taking a lot of > > CPU time (though, strangely, not always). > > > I'm using the latest SVN version of the Google App Engine Helper for > > Django. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
