Choosing Rails vs. Django based on performance and scalability [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by 开发者_如何学编程facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

I'm currently working on a side project (that hopefully will grow into something more), and right now its strictly static front-end stuff; HTML, CSS and jQuery. So in the meantime, I have time to do heavy research on choosing Ruby on Rails vs. Python/Django.

I've read countless articles comparing the two, which usually come down to "what language do you prefer?" and considerations of the development community.

My question here is strictly of a technical nature, comparing the frameworks (and their respective languages) as such:

Between Ruby/Rails vs. Python/Django:

1. Which run-time performs better (any statistics or real-world examples would be great)?
2. What are the known scalability problems, and which scales better in the long run (again, any technical documentation or data to represent this would be great)?

I understand that scalability comes down to architecture, so the question is what framework and its respective tools, APIs, plug-ins, community, documentation, etc. "guides" you towards the best scalable web architecture from the "get-go"?

Thanks!

---

That's the wrong approach to thinking about the problem.

Scalability on the web comes from expanding the number of application servers rather than speeding up an individual application server.

Ruby and Python are both slow languages with problematic multithreading and problematic garbage collectors. We use them anyway because they are very good at permitting the developer to write simpler programs that do the job better. It's not worth bothering about the question, which of these two runtimes performs better.

So long as you keep good web architecture, where your application server stateless (where all state is kept in the database or in cookies, but not in server-side sessions), you should not care what the actual performance of an individual request is, so long as it is reasonable. Because if your application server is stateless, you can scale that tier horizontally to cope with any need for scalability.

---

https://stackoverflow.com/questions/91846/rails-or-django-or-something-else
Does Django scale?
Using Rails as a framework for a large website
https://stackoverflow.com/questions/3042259/django-or-rails
Rails or Django?

...

There are plenty of questions regarding this subject, and none of them answer the question - there's no right answer.

I don't think you should choose a framework on those two metrics. Unless you are building the next Facebook, both will scale to your needs. Similarly both should perform to your needs. Instead have a look at what features of the languages and frameworks appeal to your application etc.