Min requirements for running django?

102 views
Skip to first unread message

Etienne B. Roesch

unread,
May 6, 2012, 7:24:11 PM5/6/12
to django...@googlegroups.com
Hi all,

I am investigating hosting solutions for django apps, and would like to query the community on the requirements they have experienced to do so properly. On a machine that would only run django-related processes, how much RAM? Also, any tips on how to best set it up would be much appreciated. :) e.g., separate django, media, database servers, etc, is it overkill?

http://jacobian.org/writing/django-performance-tips/
http://www.djangobook.com/en/1.0/chapter20/

Thanks much in advance!

Etienne

Начаров Михаил

unread,
May 6, 2012, 11:48:56 PM5/6/12
to django...@googlegroups.com
Hi, Etienne,

I'm using django in my apps about half of a year and deploy some apps already. It's hard to say how much memory you need, because it's really depends of what work you want to do on server-side. If it's only creating a dynamic-pages and filling the database with data coming from users, I think 100MB RAM will be enough. But remember to set DEBUG=False in your settings.py in the deployed app otherwise, the amount of required memory can be much larger.
And take a look on deployment section in django documentation. It really helps.

With love from Russia, 
Mikhail


Etienne

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.





--
Всего доброго!
Начаров Михаил

Daniel Sokolowski

unread,
May 7, 2012, 11:02:24 AM5/7/12
to django...@googlegroups.com
In my experience I can say Django is light on memory (compared to Wordpress
at least). I would also say that 100MB is plenty as mentioned by Mikhail.

Did a little study recently where freshly started 21 apache instances would
take 60 MiB, when all of our sites were hit it jumped 240 MiB --- see it
here http://blog.klinsight.com/2012/04/apache-prefork-vs-woker.html

Furthermore for simplicity I would serve both your static and Django from
the same apache instance using mod_wsgi; and use SQLite3 as the database -
you don't need a different database unless you are doing a large number of
congruent writes. I have site with 700 active users and 15,000 page hits per
month and not once did we get yet the SQLite3 write time out error and
performance tests show homepage loaded within 1 second:
http://loadimpact.com/load-test/ryatt.ca-78d92cca8f6adf72469144d5d30e39be

Daniel.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to
django-users...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.



Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/ or http://klinsight.com

Reply all
Reply to author
Forward
0 new messages