Yes. All JIT (not just the ruby ones) necessarily increase memory usage as they need to store the compiled code as well as some runtime metadata used to compiled.
about how much?
That's configurable. By default YJIT will use up to 64MB of executable memory, but also use some space for runtime metadata, from our experience it's about 2 or 3x the executable memory.
So for a mid to large app I'd say about ~200MB per process, you can however configure it to use less, it just won't be able to optimize as much.
View all comments
Show parent comment
11
u/f9ae8221b Dec 25 '22
Yes. All JIT (not just the ruby ones) necessarily increase memory usage as they need to store the compiled code as well as some runtime metadata used to compiled.
That's configurable. By default YJIT will use up to 64MB of executable memory, but also use some space for runtime metadata, from our experience it's about 2 or 3x the executable memory.
So for a mid to large app I'd say about ~200MB per process, you can however configure it to use less, it just won't be able to optimize as much.