django-nonrel performance on Google App Engine

What is the performance impact of developing applications on Google App Engine using django-nonrel as opposed to webapp?

I am aware that there is not much difference between webapp开发者_开发百科 and the django which is included in google appengine already, but the question is more around the fine work the guys have been doing over at : http://www.allbuttonspressed.com/

Thanks

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 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.