In order to execute Ruby code as fast as possible, Rubinius has the ability to compile Ruby code all the way down to machine code when it detects that a method is heavily used. In Rubinius, the system that manages this process is its JIT. In today’s post, I’ll be giving an overview of the various players involved in the path that code takes to get from source to machine code. Without further ado,
![Making Ruby Fast: The Rubinius JIT](https://cdn-ak-scissors.b.st-hatena.com/image/square/a88c6003b668a4f2b56d6381f9b844e16585eac9/height=288;version=1;width=512/https%3A%2F%2Fblog.engineyard.com%2Fhubfs%2Fsupport-panda-headline.png%23keepProtocol)