4 ms·

This is in no way a good test. Yes, Rubinius takes longer to load than MRI. It'a also JITed, so it needs time to warm up to start screaming. Also, this is in

This is in no way a good test. Yes, Rubinius takes longer to load than MRI. It'a also JITed, so it needs time to warm up to start screaming. Also, this is in dev mode... did you disable Rack::Lock? MRI can only handle 1 request at a time, Rubinius can handle whatever your concurrency level is (assuming you've removed Rack::Lock from your environment)

resca79 13y ago
Rails 4 is thread safe and I used puma as server Also the app is in production mode and the db pool is 16
- timdorr 13y ago
  Can you post a link to the app? Have you considered running the TechEmpower benchmark app? https://github.com/TechEmpower/FrameworkBenchmarks https://github.com/TechEmpower/FrameworkBenchmarks
- fbernier 13y ago
  Rails 4.0.0 application starting in development on http://0.0.0.0:3000 http://0.0.0.0:3000 This most likely means Rack::Lock is used in your test.
  - resca79 13y ago
    I used the following command rails s puma -e production
  - rubiquity 13y ago
    Rack::Lock was removed as a default in Rails 4.
timdorr 13y ago
> This is in no way a good test. Yes, Rubinius takes longer to load than MRI. It'a also JITed, so it needs time to warm up to start screaming. This is a fair point. You should run ab multiple times over a longer duration of time. 5 seconds seems like a short time to declare an absolute winner.
- resca79 13y ago
  Honestly I declare no winner. This is a very simple test. I wanted to share with you, to even get tips thanks
rubiquity 13y ago
It's a Rails 4 app. Rack::Lock is removed by default.