From: "smcgivern (Sean McGivern)" Date: 2022-11-07T20:51:05+00:00 Subject: [ruby-core:110647] [Ruby master Bug#19101] madvise(free) was broken in 3.1? Issue #19101 has been updated by smcgivern (Sean McGivern). ioquatix (Samuel Williams) wrote in #note-5: > I am copying all the discussion from GitHub here: > [...] > smcgivern 12 hours ago > > > Thanks for looking at this, @ioquatix! > > > > For a bit of background: @mttkay and I work together, and we were investigating a case of seemingly high RSS for fluentd, which uses Async::HTTP in plugins that have HTTP servers. (Nice work on the Async series of libraries, by the way.) > > > >It turned out that this was due to LazyFree memory - from MADV_FREE - being included in RSS, and not an actual increase in 'real' memory usage by fluentd. Incidentally, Go reverted their use of MADV_FREE due to similar concerns: golang/go#42330 In a link format that works here: https://github.com/golang/go/issues/42330 ---------------------------------------- Bug #19101: madvise(free) was broken in 3.1? https://bugs.ruby-lang.org/issues/19101#change-99988 * Author: ioquatix (Samuel Williams) * Status: Closed * Priority: Normal * Assignee: ioquatix (Samuel Williams) * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONE ---------------------------------------- https://github.com/ruby/ruby/commit/77f3319071e600a2aafaa9863b892dfd3c1da343#r88774579 We need to investigate why this was done, how to fix it, and how to prevent regressions in the future. -- https://bugs.ruby-lang.org/ Unsubscribe: