From: "maciej.mensfeld (Maciej Mensfeld) via ruby-core" Date: 2024-06-18T08:51:37+00:00 Subject: [ruby-core:118338] [Ruby master Bug#20462] Native threads are no longer reused Issue #20462 has been updated by maciej.mensfeld (Maciej Mensfeld). I also believe it can multiple any potential issues with resources leakage. Not sure yet what is causing this but working with a Rails user that sees this: > I wrote a little script that creates 100k threads and can report 3.3.3 allocates way more memory than 3.2.x > 3.2.2 - Memory allocated: 49603264 bytes > 3.3.3 - Memory allocated: 104926404080 bytes ---------------------------------------- Bug #20462: Native threads are no longer reused https://bugs.ruby-lang.org/issues/20462#change-108844 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Ruby used to reuse native threads in order to amortize the cost of making a pthread. For example this program: ```ruby ntids = 1000.times.map { Thread.new { Thread.current.native_thread_id }.value } p ntids.uniq.length ``` With Ruby 3.2.0, this would return 1. With Ruby 3.3.x, it returns 1000. It means we cannot amortize the cost of a pthread for short lived threads. I was able to bisect this to commit be1bbd5b7d40ad863ab35097765d3754726bbd54. But the change is big so I don't know how to fix it. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/