On 16/11/2012, at 3:28 PM, Michal Fojtik wrote: <snip> > So I did a quick test yesterday night (or today morning ;-) where I tried > to use TorqueBox to run Deltacloud API and then do a benchmark using 'ab' > command (1000 request, concurrency set to 5) and I got interesting results: > > 1. Deltacloud API works like a charm on jRuby (no problem, no exceptions, ...) > 2. The performance is 2x better with jRuby than using MRI > 3. Using MRI with 'thin' reveals that 5% of requests just failed without any > reason, > where using jRuby all request were served properly. > 4. The memory used by both are almost the same (well JVM use a bit more > memory, but > at least it does not grow ;-) > > There are two drawbacks that I observed: > > 1. The boot time of JVM (jRuby) is a bit longer than MRI - but that is not an > issue. > 2. There is no code reloader for Sinatra in Torquebox (at least I tried to > find one > but no luck) > > So to wrap this up, I'm very surprised by the jRuby performance and also by > compatibility > between MRI and jRuby (1.7.0).
Do you reckon it's worthwhile for the Aeolus Release Cabal to look into having Torquebox be a "supported" upstream platform for Aeolus in a future release? Obviously not near term, but down the track if/when it makes sense. Regards and best wishes, Justin Clift -- Aeolus Cloud Evangelist http://www.aeolusproject.org
