Rails and Grails: A language shootout?

Following the benchmarking, I think it’s a very good idea from Graeme to stop benchmarking until Grails gets some optimizations. Currently performance should not be a big concern for the Grails developers. Keeping up the good work with implementing features and fixing bugs should stay their main concern.

When looking at the Grails versus Rails benchmarks, I thought this might be more about languages than web frameworks.


Rails: Ruby
Ruby: Ruby/C
MySQL: C
MySQL driver: C/Ruby
Mongrel: Ruby/C

Grails: Java/Groovy
Groovy: Java/Groovy
Java: Java/C
MySQL: C
MySQL driver: Java
Tomcat: Java


(Correct me if I’m wrong please)

It’s great news to me that for example mongrel is primary ruby. Some years ago when I did some projects with Ruby, a lot of stuff was written in C and needed to be compiled, which is always a lot of pain. Also the code looks quite good and clean. And they thought about performance:


# Does the majority of the IO processing.
# It has been written in Ruby using
# about 7 different IO processing strategies
# and no matter how it's done
# the performance just does not improve.
# It is currently carefully constructed
# to make sure that it gets the best possible
# performance [...]


Good to see.

So is this about Rails versus Grails or Ruby versus Groovy or C versus Java? But as I said in the beginning, I think it’s a very good idea from Graeme to stop benchmarking until Grails gets some optimizations

You can leave a Reply here. Of course, you should follow me on twitter here.