1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

YJIT: Update yjit.md about mem size (#9687)

Browse Source
This commit is contained in:
Takashi Kokubun 2024-01-24 10:26:57 -08:00 committed by GitHub
parent 1702528258
commit 303fef8752
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/yjit/yjit.md
View File

@ -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 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. 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, `--yjit-exec-mem-size=48` is the default since Ruby 3.3.1,
but smaller values like 32 MiB or 48 MiB might make sense for your application. 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. While doing so, you may want to monitor `RubyVM::YJIT.runtime_stats[:ratio_in_yjit]` as explained above.
### Enabling YJIT lazily ### Enabling YJIT lazily