diff options
| author | Alan Wu <alanwu@ruby-lang.org> | 2023-11-10 19:08:05 -0500 |
|---|---|---|
| committer | Alan Wu <alanwu@ruby-lang.org> | 2023-11-10 19:08:05 -0500 |
| commit | cdaca574ced468e21725703504537d0f5424b8f9 (patch) | |
| tree | f5a86ea73fb4947da7255937e18c4df91b156dca | |
| parent | f5fa90fe0bf8f606e80a86f02f939003e7aa6834 (diff) | |
[DOC] NEWS.md update about code GC
See <https://github.com/ruby/ruby/pull/8865> and
50402db5a7d3bb2a9a93d63a63295b4d85a68088
| -rw-r--r-- | NEWS.md | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -237,9 +237,10 @@ changelog for details of the default gems or bundled gems. * This can also be used to enable YJIT only once your application is done booting. `--yjit-disable` can be used if you want to use other YJIT options while disabling YJIT at boot. -* Option to disable code GC and treat `--yjit-exec-mem-size` as a hard limit - * Can produce better copy-on-write behavior on servers using unicorn and forking -* `ratio_in_yjit` stat produced by `--yjit-stats` is now avaiable in release builds, +* Code GC now disabled by default, with `--yjit-exec-mem-size` treated as a hard limit + * Can produce better copy-on-write behavior on forking web servers such as `unicorn` + * Use the `--yjit-code-gc` option to automatically run code GC when YJIT reaches the size limit +* `ratio_in_yjit` stat produced by `--yjit-stats` is now available in release builds, a special stats or dev build is no longer required to access most stats. * Exit tracing option now supports sampling * `--trace-exits-sample-rate=N` |
