4 ms·
Hello Mnutt, I'm running the test into an MBA 11", it's very very slow, this is why this numbers are so different. The MBA is a good development machine as ever
by antirez 16y ago
Hello Mnutt, I'm running the test into an MBA 11", it's very very slow, this is why this numbers are so different. The MBA is a good development machine as everything seems slow even if it is just a bit slow :)
Btw the PHP code is reloading the template at every request for sure. I pasted the example code I used on the blog.
- mnutt 16y agoSorry, 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.