Benoit Daloze

There is great progress here due to improvements to inner contexts in Truffle (upcoming PR, but seems almost ready). With that it's convenient and efficient to use inner contexts for...

There is a Graal.js backend in execjs since 22.2 or earlier, and it works well: https://github.com/rails/execjs/blob/master/lib/execjs/graaljs_runtime.rb It is automatically selected if running with `TRUFFLERUBYOPT="--jvm --polyglot"`, TruffleRuby+GraalVM and `js` is installed...

Probably `using` should go to the closest module body or so, similar to how visibility looks for the module body frame. I think actually `using` was never intended to work...

It looks like compilation fails because it does not use the GraalVM LLVM toolchain. The reason seems to be it's not a usual extension (see files at https://github.com/garaio/xapian-ruby) and instead...

Actually there is probably an even easier way to check if that solves it, with `RUBYOPT=-rmkmf gem install xapian-ruby`. I tried that, but it fails: ``` ... checking whether the...

Thanks for the report. Interesting, I've never heard about this Digest algorithm before.

@dogweather No, that's most likely https://github.com/oracle/truffleruby/issues/2577 and that's solved on master/dev builds.

10 seconds is likely not enough for TruffleRuby to warmup and important methods to be JIT-compiled.

@deepj Could you also try with 1 route on roda on puma? https://github.com/jodosha/ruby-web-bench/blob/3babcb8a86f47673504632e19d1c4369ea684d0b/apps/roda-10000.ru is a bit weird honestly, 32000 lines, 10000+ blocks (so it's going to be very slow to...

Thanks for sharing those results, they indeed look unexpectedly slow. We'll look into it.