Who is less memory demanding Django or Rails?

Question

Django

Assume 1 small site with average traffic.

There is no way to find out in practice.
Not a chillivar for.

Answer 1

I currently have 8 django projects on my VPS (the largest is treeio) and gitlab, which is on rails. RAM usage:
uwsgi - 81Mb
ruby1.9.1 - 264Mb

Answer 2

The question is not specific. Let's say django with flat pages lives on a weak vpsky. Here is the approach to the architecture of the site.
Front nginx, caches, OS optimization. In principle, the standard approach.
I will make a reservation right away, my site lives on sqlite. The question is not correct, 1 small site will be equally good on Django and on rails, and equally bad if it is crookedly written.

Answer 3

The default rail app with one model, haml templating engine and mysql database created through generators loses to the default django application with one model, standard templating engine on my server, both applications run under unicorn and gunicorn respectively, go through nginx.
What is the reason? Probably, as noted above, in caches, in the optimization of a particular application.
But, as practice has shown, the convenience of developing with a familiar tool compensates for the initial difference in performance - since with proper knowledge, you can make any application work quickly.

Answer 4

Depends on many factors. The same Rails, depending on which environment is deployed, JRuby clearly consumes much more than MRI. Moreover, consumption is influenced by a number of very non-obvious factors, such as the template engine used, the number of models, their attributes, validators, etc.
Saving memory is not worth it to use a less familiar and convenient tool.

Answer 5

Rails is historically much more power hungry. loads a bunch of libraries (although the situation seems to be gradually changing for the better lately). Django eats less.