From a6553e4ad314d3c86144ca605b5eb32edb437dda Mon Sep 17 00:00:00 2001
From: Alan Wu <XrXr@users.noreply.github.com>
Date: Tue, 7 Apr 2026 17:34:27 -0400
Subject: [PATCH] Don't build JITs for interpreter speed baseline

We found out that as expected, the interpreter runs slower on some micro
benchmarks when the build contains ZJIT. As ZJIT builds optimize for
when ZJIT is enabled, it's more fair that we compare `--enable-zjit`
speed against a `--disable-yjit --disable-zjit` interpreter baseline.
---
 rubies.yaml | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)

diff --git a/rubies.yaml b/rubies.yaml
index e3eca8813..ff87441df 100644
--- a/rubies.yaml
+++ b/rubies.yaml
@@ -43,7 +43,13 @@ builds:
       - --enable-yjit
       - --enable-zjit
 
-  ruby-metrics-app-prev:
+  ruby-metrics-dev-no-jit:
+    <<: *build_base
+    configure_args:
+      - --disable-yjit
+      - --disable-zjit
+
+  ruby-metrics-app-prev: &prev_build
     <<: *build_jit
     # In order to build "prev" ruby the same way we build "prod" ruby
     # we build it from source, so we use a tag that represents a recent release.
@@ -53,6 +59,12 @@ builds:
       # Ruby 3.3 only supports yjit.
       - --enable-yjit
 
+  ruby-metrics-prev-no-jit:
+    <<: *prev_build
+    configure_args:
+      - --disable-yjit
+      - --disable-zjit
+
   truffleruby-dev:
     install: ruby-build
 
@@ -70,11 +82,11 @@ runtime_configs:
     opts: *zjit_stats
 
   prod_ruby_no_jit:
-    build: &prod_jit ruby-metrics-app-jit-prod
+    build: ruby-metrics-dev-no-jit
     opts: *no_jit
 
   prod_ruby_with_yjit:
-    build: *prod_jit
+    build: &prod_jit ruby-metrics-app-jit-prod
     opts: *yjit
 
   prod_ruby_zjit:
@@ -82,11 +94,11 @@ runtime_configs:
     opts: *zjit
 
   prev_ruby_no_jit:
-    build: &prev_ruby ruby-metrics-app-prev
+    build: ruby-metrics-prev-no-jit
     opts: *no_jit
 
   prev_ruby_yjit:
-    build: *prev_ruby
+    build: ruby-metrics-app-prev
     opts: *yjit
 
   truffleruby-dev: