Are there any tests comparing the use of appropriate django, rails memory and PHP frameworks?

I need to run a web server with many services on an embedded server with limited RAM (1 GB, no sharing). There will be no more than 100 users. I will have services such as a forum, small games (javascript or flash), etc.

My team knows Ruby on Rails very well, but I'm a little worried about using Rails memory. I really don't want to start the trolls here, but I wonder if there are serious (i.e. documented) tests comparing Rails, Django, CakePHP or any other PHP framework?

Could you point out the benchmarks or give me your opinion on the use of Rails memory? Please, please, not a troll.

+5
source share
3 answers

In terms of memory usage, it's usually Python> Ruby> PHP, which of course leads to Django> Rails> CakePHP. Not just memory, but also tends to hold on to raw performance. EDIT: It's also worth noting that there are, of course, no absolutes. There are many use cases in which Ruby will beat Python, hands down. I think we can all agree that Ruby and Python will always beat PHP, though :)

Here's a straightforward tripartite benchmarking (with Symfony on the PHP side) that states: http://wiki.rubyonrails.com/rails/pages/Framework+Performance. , , , :)

, , Django , Rails . , , . , ( Apache nginx/lighttpd ..), , , .

, , , Rails, Rails, Rails.

+3

, Rails , 64- (. 95-100 thin -). PHP, , , .

+1

All Articles