YJIT Benchmarks

YJIT metrics from the yjit-bench suite as of 2024-09-06
Using the geomean of the headline benchmarks for x86 YJIT 3.4.0dev is
  • 74.9% faster than CRuby 3.4.0dev
  • 2.4% faster than YJIT 3.3.4
On railsbench it is
  • 77.9% faster than CRuby 3.4.0dev
  • the same speed as YJIT 3.3.4
Latest Full Details:
YJIT 3.4.0dev build configuration
Ruby
ruby 3.4.0dev (2024-09-06T00:32:47Z :detached: 81b74c9fad) +YJIT [x86_64-linux]
Configure args
--disable-install-doc --disable-install-rdoc --enable-yjit
Compiler
gcc (Ubuntu 13.1.0-8ubuntu1~20.04.2) 13.1.0

Latest Headlining Results vs CRuby

These "headlining" benchmarks are used for the above measurements. There are more benchmarks on the Full Details Page.

Performance on Headline Benchmarks

0.0 0.5 1.0 1.5 2.0 2.5 CRuby 3.3.4 CRuby 3.4.0dev YJIT 3.3.4 YJIT 3.4.0dev activerecord chunky-png erubi-rails hexapdf liquid-c liquid-compile liquid-render lobsters mail psych-load railsbench rubocop ruby-lsp sequel geomean* 1.01 2.20 2.23 0.94 1.66 1.87 0.92 1.86 1.73 0.99 1.64 1.78 1.03 1.45 1.50 0.99 1.44 1.43 0.99 2.52 2.63 0.97 1.53 1.50 1.00 1.48 1.44 0.98 1.51 1.66 0.98 1.75 1.74 0.98 1.74 1.83 0.97 1.66 1.69 1.01 1.37 1.37 0.98 1.68 1.72 Speed of each Ruby implementation relative to the baseline CRuby measurement. Higher is better.

Memory Usage on Headline Benchmarks

0.0 0.2 0.4 0.6 0.8 1.0 1.2 1.4 CRuby 3.3.4 CRuby 3.4.0dev YJIT 3.3.4 YJIT 3.4.0dev activerecord chunky-png erubi-rails hexapdf liquid-c liquid-compile liquid-render lobsters mail psych-load railsbench rubocop ruby-lsp sequel geomean* 0.92 1.17 1.19 1.24 0.88 1.35 1.06 1.09 1.11 0.81 1.56 1.40 1.06 1.18 1.21 1.06 1.10 1.15 0.99 1.15 1.24 1.11 1.17 1.20 1.37 1.13 1.45 1.04 1.08 1.09 1.09 1.13 1.17 1.02 1.33 1.40 0.91 1.10 0.98 1.06 1.13 1.17 1.04 1.15 1.22 Memory usage of each Ruby implementation relative to the baseline CRuby measurement. Lower is better.

YJIT Results Over Time

  •    x86_64 railsbench   
  •    x86_64 optcarrot   
  •    x86_64 liquid-render   
  •    x86_64 activerecord   
Y axis values are the total number of seconds to run the benchmark one time - lower is better.