JRuby startup costs [was: Process-level fork on OpenJDK...is it madness?]

[Clemens Eisserer]

Hi Oliver,

> Another more subtle aspect is that our interpreter gets "hot" *very*
> quickly, since it's running the same code over and over again
> regardless of what Ruby code is executing. If all that Ruby code were
> JVM bytecode, each piece would have to get "hot" to run fast...so
> interpreting wins there too.

Hmm, from what I understand, hotspot's interpreter is already
"super-hot" right after startup.
Whereas JRuby's interpreter is jvm bytecode that needs to be compiled
by a compiler, hotspot's interpreter is *hand-tuned* low-level
assembly.

- Clemens