2 ms·
For anyone curious, we've been working to reduce the memory overhead and have added some stats to keep track of memory usage over time. On this graph, you can s
by maxime_cb 4y ago
For anyone curious, we've been working to reduce the memory overhead and have added some stats to keep track of memory usage over time. On this graph, you can see a comparison with the CRuby interpreter:
https://speed.yjit.org/memory_timeline#railsbench https://speed.yjit.org/memory_timeline#railsbench
- greenpeas 4y agoWhat happened on jun 14? (the dramatic drop in memory usage) Edit: I guess this (https://github.com/ruby/ruby/pull/5944 https://github.com/ruby/ruby/pull/5944) PR was merged.
- maxime_cb 4y agoYes. Prior to that point we used to allocate a large chunk of executable memory upfront. We switched to mapping that memory on demand, and that alone was a huge improvement.