Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0
by timdorr on Wednesday October 09, 2013 @09:41AM
(#6521147)
> 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.
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0
by resca79 on Wednesday October 09, 2013 @09:47AM
(#6521176)
Honestly I declare no winner. This is a very simple test.
I wanted to share with you, to even get tips
thanks
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0
by resca79 on Wednesday October 09, 2013 @09:37AM
(#6521128)
Rails 4 is thread safe and I used puma as server
Also the app is in production mode
and the db pool is 16
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0
by timdorr on Wednesday October 09, 2013 @09:43AM
(#6521158)
Can you post a link to the app? Have you considered running the TechEmpower benchmark app? https://github.com/TechEmpower/FrameworkBenchmarks
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0
by fbernier on Wednesday October 09, 2013 @09:44AM
(#6521168)
Rails 4.0.0 application starting in development on http://0.0.0.0:3000
This most likely means Rack::Lock is used in your test.
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0
by resca79 on Wednesday October 09, 2013 @09:49AM
(#6521187)
I used the following command
rails s puma -e production
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)