Does running Django on GoogleAppEngine, as opposed to the default WebApp2 framework, consume additional resources? Any metrics?
相关问题
- Django __str__ returned non-string (type NoneType)
- java.lang.NullPointerException at java.io.PrintWri
- Django & Amazon SES SMTP. Cannot send email
- Django check user group permissions
- Django restrict pages to certain users
相关文章
- Is there a size limit for HTTP response headers on
- Profiling Django with PyCharm
- Why doesn't Django enforce my unique_together
- MultiValueDictKeyError in Django admin
- Django/Heroku: FATAL: too many connections for rol
- appcfg.py command not found
- Django is sooo slow? errno 32 broken pipe? dcramer
- Google app engine datastore string encoding proble
From the mailing list, I've seen multiple comments on Django instances taking significantly longer to start up if cold. This would be noticeable if your app is rarely used.
From my app's log it looks like the first request took about 4 seconds to start up.
My Django instances use 41-43MB. Not sure about webapp2.
If you're using Django-nonrel as an ORM, I'm sure there's a few cycles spent in the ORM translation, but I doubt it's significant. My Tastypie REST layer can take anywhere between 40-120ms for the same request, it looks like that performance is dictated more by the datastore than anything else.