This PR prints YJIT's memory-related stats besides RSS after each run of a benchmark.
When we check the YJIT code size on yjit-bench, we often use --yjit-stats and look at what it prints. However, because --yjit-stats generates more code than --yjit, it has some unwanted noise. To check the actual code size, we need to look at RubyVM::YJIT.runtime_stats without using --yjit, and this PR lets the harness do that.
This PR prints YJIT's memory-related stats besides RSS after each run of a benchmark.
When we check the YJIT code size on yjit-bench, we often use
--yjit-stats
and look at what it prints. However, because--yjit-stats
generates more code than--yjit
, it has some unwanted noise. To check the actual code size, we need to look atRubyVM::YJIT.runtime_stats
without using--yjit
, and this PR lets the harness do that.Example: