From 45e177957697b15bc735c938112972d8a68ef610 Mon Sep 17 00:00:00 2001 From: Takashi Kokubun Date: Wed, 24 Jan 2024 10:20:33 -0800 Subject: [PATCH] YJIT: Update yjit.md about mem size --- doc/yjit/yjit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/yjit/yjit.md b/doc/yjit/yjit.md index 02f8dd794888b2..e6446e3ed1b66b 100644 --- a/doc/yjit/yjit.md +++ b/doc/yjit/yjit.md @@ -243,8 +243,8 @@ which often consumes more memory than JIT code. Generally, YJIT adds memory over 3-4x of `--yjit-exec-mem-size` in production as of Ruby 3.3. You should multiply that by the number of worker processes to estimate the worst case memory overhead. -We use `--yjit-exec-mem-size=64` for Shopify's Rails monolith, which is Ruby 3.3's default, -but smaller values like 32 MiB or 48 MiB might make sense for your application. +`--yjit-exec-mem-size=48` is the default since Ruby 3.3.1, +but smaller values like 32 MiB might make sense for your application. While doing so, you may want to monitor `RubyVM::YJIT.runtime_stats[:ratio_in_yjit]` as explained above. ### Enabling YJIT lazily