So your benchmark only have tested against the small "Hello World" app. Maybe that's why I suggested that Padrino framework is pretty ideal for small/personal/API projects for fastest responses.
Have you tried benchmarking your one of biggest padrino apps?
Check it out here: https://github.com/DAddYE/web-frameworks-benchmark/tree/more...
Yep, speed is 4-6x faster, but most important for me is memory usage is much much less.
On every Rails project I need to use monit/god to stop/start when for xx cycles memory is > 100mb or so. Without that a rails project can sucks 1-2gb of ram.
Isn't quite normal to my standards, in fact generally Padrino doesn't need more than 70mb. But here a lot of work must to be do.
You said there are more than "Hello World" benchmarks? I looked at the link that you provided and then looked at this source code of the Padrino app and its still "Hello World":
https://github.com/DAddYE/web-frameworks-benchmark/blob/more...
I expected to see something more than just Hello World app.
I am trying to see why you are suggesting me that Padrino is better than Rails. :-) Sounds like you are completely against Rails. Maybe I am wrong.
Which is: https://github.com/DAddYE/web-frameworks-benchmark/blob/more...
With a layout: https://github.com/DAddYE/web-frameworks-benchmark/blob/more...
Not a very very complex use case but a bit more than a `hello world` app.
I love Rails, Im using i.e. ActiveRecord in 90% of my projects. Beside that I ported 162 apps over Padrino not because I've free time to spend but because I need decent performances (without kongfu with mem/redis caching) with less memory usage.
Try to browse rails (minus ActiveRecord) source code and padrino source code to understand what I mean.