Hello,
A while back I watched Jimmy on C9 talking about how IronRuby had a
hybrid approach to execution only jitting after a code path had been
run a couple times. Is there any way to control this. I’d like to
experiment with either (1) turning off compilation and (2) forcing
immediate compilation. The scenario is that there are times when i
might be able to get away with the “compilation penalty” and I’d like
to play around with doing just that.
Is there anywhere I can find information on how to do this with the DLR?
Thanks,
Martin
There is. You can set “NoAdaptiveCompilation” options on language setup
when creating ScriptRuntime. Command line option is
-X:NoAdaptiveCompilation.
We’ll also add “CompilationThreshold” option soon, which specifies the
number of iterations before we start compiling.
Tomas
Thanks Tomas!
I also found the InterpretedMode flag as well.
I’ve been looking a little more and it looks like the bulk of our
problems are related to running IronRuby code through the VS.NET
debugger. We had a script that was taking 15 seconds or more to run
but runs in under a half second when we run our app outside of Visual
Studio. Compiling does confer some pretty serious advantages though.
Thanks!
Martin
On Tue, Nov 10, 2009 at 5:14 PM, Tomas M.
Hey Tomas,
Are you planning on allowing the CompilationThreshold option to be
set… so basically I’d envision:
- app startup CompilationThreshold = 0
- warm up and jit all the ruby code
- after startup is finished set CompilationThreshold = 50 (or
something) so we can issue quick calls to the already compiled code.
That would be pretty cool if it could work that way.
Thanks,
Martin
On Tue, Nov 10, 2009 at 5:14 PM, Tomas M.