Django-nonrel performance on Google App Engine?

Django imposes a fairly significant startup overhead over lighter weight frameworks like Webapp (which only use parts of Django, optionally) - anything up to an additional 500 milliseconds if you believe the benchmarks. This can be alleviated or eliminated with warmup requests and always on instances After startup, I wouldn't expect a significant difference in efficiency - most of the time spent is going to be waiting for RPCs in any framework - but you may find these benchmarks of template and framework performance interesting.

Django imposes a fairly significant startup overhead over lighter weight frameworks like Webapp (which only use parts of Django, optionally) - anything up to an additional 500 milliseconds if you believe the benchmarks. This can be alleviated or eliminated with warmup requests and always on instances. After startup, I wouldn't expect a significant difference in efficiency - most of the time spent is going to be waiting for RPCs in any framework - but you may find these benchmarks of template and framework performance interesting.

Thanks for this answer. Does this mean that the first time the application is hit, there is a 500 millisecond wait? – user791793 Jun 18 at 11:15 @user791793 Unless you're using always on instances, or the infrastructure sent a warmup request to the app first, yes.

– Nick Johnson Jun 20 at 1:31.

Django is not included with appengine, appengine just uses the django templating library. Webapp is another framework which is derived from webob. Coming to django-nonrel Django-nonrel is a project which allows developers to run native Django projects (including Django's ORM) on non-relational databases, one of which is Google App Engine's Datastore.(This is all in addition to the standard traditional SQL databases that have always been supported by Django.) App Engine does come with some Django support, but this is mainly only the templating and views.

Other tools that allow for rapid development such as forms, the built-in administration interface or Django authentication just won't run out-of-the-box. Django-nonrel changes this for Django developers. Django-nonrel mainly is for running your current django projects on appengine without much efforts.

Coming to performance impact, I don't think there will be much of impact on performance while opting for django-nonrel.

1 Django is included in app engine -- just not all of it can be used as is. See here: code.google. Com/appengine/docs/python/tools/… .

In addition, as far as I can tell, the only relevant part of this is "i don't think there will be much of impact on performance while opting for django-nonrel. " Do you have anything to back this up, one way or the other? Any qualifications on this?

– Elliot de Vries Jun 15 at 15:00.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.