fangzx schrieb:
> I have read this article 'Why is Groovy so slow?':
>
http://www.jroller.com/rants/entry/why_is_groovy_so_slow>
> I planed to use Groovy in my new project based on JBoss Seam, but now I must
> wait.
> Can anyone give me some advice?
Russel basically answered to this very good,I just want to add that the
conclusions in the blog are not right for the languageGroovy, they are
just right for the current implementation. We will spend much time in
the next year to get Groovy running much faster. Then a word to these
benchmarks...
The loop is a very good example for hotspots abilities to unroll a loop,
skip its execution and make mostly a jump instead. The resulting Groovy
code is much complexeratm, making it much more difficult for hotspot to
do its job. What we will try now is to make alternative paths in the
code depending on when a custom MOP is active or not. I very much
believe, that when this is implemented, the the code will be not only
much faster, but also much more compareable to Java.
Most possibly we won't able to be as fast Java, but I am sure we will be
able to get in regions where we will have an acceptable speed even for
things like that loop ;)
Oh.. one more thing... unlike normal Java code it makes much of a
difference if you use the server VM to execute Groovy sscripts
bye blackdrag
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email