I've noticed this too -- there seem to be more frequent reloads during the (GMT) evening.
I add a message to the log the first time an instance is created (by tracking a module-level variable) so it's easy to see the effect on the ms-cpu figure. One thing I've noticed by the way is that it *isn't* really unzipping that takes time, it's just loading django that hurts. I've tried using an uncompressed django dir and the figures are about the same. What kind of slowdown are you seeing with appengine-patch btw? What's the typical ms-cpu reading for those first requests? I'm using the django helper and I'm logging 1500-1800 ms-cpu for each initial call. This is enough to delay rendering but not enough to timeout a request, which I guess is something. Has anyone done any profiling on where the CPU is being spent when django is loaded? Would it be possible to do some of the monkey patching on a custom django before deployment (ie actually change the django source files)? cheers Michael On Feb 10, 4:07 pm, conman <constantin.christm...@googlemail.com> wrote: > I am not quite sure, but it seems to me the zipimport/loading of our > app is only a problem in the early evening (Germany)/forenoon PST > It's now 8:00 am PST and our app failes serving - just on time as it > was the days before. > > It's not that we get more traffic/less traffic at this time of the > day. > > When accessing our app at this time it is reacting really slow and > starts serving 500 errors. > > After some hours it gets better and approx. 3-4 h later it works like > a charm again. > Are there backups scripts running at that time of the day?? > > We are using django 1.0 via app engine patch - btw: great work > Waldemar! > > On 10 Feb., 14:09, Waldemar Kornewald <wkornew...@gmail.com> wrote: > > > Hi Dan, > > > On Feb 10, 5:05 am, Dan Sanderson <dansander...@google.com> wrote: > > > > As for bundling Django, we plan to upgrade the bundled Django with the > > > next > > > major version of the Python runtime environment. Upgrading Django 0.96 to > > > 1.0 in place does not meet our criteria for a backwards compatible change, > > > and so cannot happen without a major version bump. > > > It's not really a pratical solution to have an unpatched Django > > release which gets monkey-patched. The django-helper's monkey-patching > > technique works at a small scale, but if you need the admin interface > > and the other interesting Django features you have to stay compatible > > with very specific implementation details (this can even happen for > > minor features), so even upgrading between API-compatible bugfix > > releases (Django 1.0 => 1.0.2) could break at least django-helper > > which means you break a whole website. Thus, you couldn't even provide > > bugfix releases without introducing a new API version. > > > I can see only two practical options: > > > 1. Remove Django from App Engine and let everyone take care of > > installing it, manually. That's what most of us already do. We just > > need a solution for the request timeouts, but maybe they're related to > > the zipimport bug which finally got identified? > > > 2. Patch Django in-place and bundle the pre-patched version with App > > Engine, so we get a real Django port. This is only acceptable if you > > support almost all of Django's features, including the admin > > interface. Even better, Django 1.2 or 1.3 might come with support for > > query backends, so it could be possible to provide a backend that > > makes Django's Model class compatible with App Engine. I've started > > documenting the high-level changes > > here:http://code.djangoproject.com/wiki/AppEngine > > The discussion is > > here:http://groups.google.com/group/django-developers/browse_thread/thread... > > > Maybe I missed something. What plan did you have? > > > 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 -~----------~----~----~----~------~----~------~--~---
