4 ms·
Sorry, I just posted numbers to show the difference between dev mode and production mode. I guess what I don't understand is: if you're running a site in devel
by mnutt 16y ago
Sorry, I just posted numbers to show the difference between dev mode and production mode.
I guess what I don't understand is: if you're running a site in development, isn't 250 req/s enough? And if you're running in production, do you need to reload the template on each request?
Unless you're just using this as an example indicative of the fact that ruby/rails could surely stand to be faster, in which case I completely agree. As does Ilya Grigorik: http://www.igvita.com/2010/06/07/rails-performance-needs-an-overhaul/ http://www.igvita.com/2010/06/07/rails-performance-needs-an-...
- antirez 16y agoOk my fault that did not said this in the blog post. I was playing with Sinatra, and my real page involved substituting a few nested templates, with different parts of the site. News box, comments boxes, ... The result was... 30 requests per second once a few templates started to stack, and with mostly toy code. It is easy how things can get worse just doing a few mistakes along this path.