News for hackers. Stuff that matters.
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0 by JimmaDaRustla on Wednesday October 09, 2013 @09:18AM (#6521031)
So, MRI is way faster than Rubinius in this case? Interesting...
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0 by mrinterweb on Wednesday October 09, 2013 @10:18AM (#6521354)
Not necessarily. No warmup time was allowed for rubinius's cache. Also we don't know how concurrency was being handled. Rubinius should be able to utilize multiple cores. More information about the hardware, rails app, way that the puma server is being started, warmup time, duration of request time spent on the database, etc should be made available before any remote conclusion like which one is faster can be made.
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0 by JimmaDaRustla on Wednesday October 09, 2013 @10:36AM (#6521471)
That was my concern - Rubunius' selling point is concurrency, so I'm sure there is an approach to implementation, which is why I've never used it.
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0 by warmwaffles on Wednesday October 09, 2013 @10:24AM (#6521384)
No. Rubinius' JIT has not had time to warm up. These tests are a little unreliable. I can't find the article off hand, but the way these tests were done aren't exactly telling me anything. Power of ten tests don't do much other than show me that the tester is naive.
Re:Load Test Rails4 app ruby 2.1 MRI Vs Rubinius 2.0 by resca79 on Wednesday October 09, 2013 @09:20AM (#6521041)
yes... and I repeat it and sometimes in this case is 2x faster