-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
concurrent-ruby Fixed Thread Pool memory leak #3558
Comments
Thank you for the report, we'll look into it. |
Could you share a reproducer we can run? Note also that the JVM (and Native Image too BTW) uses up to its Xmx (which defaults to 25% of total physical RAM with G1 GC if no Xmx is passed) if it thinks it's more efficient for the GC/allocations/etc. So one thing you could try is to pass e.g. |
When running an update on a large dataset I'm seeing a big and steady memory leak with TruffleRuby. The code is proprietary but in essence it is based on a
FixedThreadPool
from concurrent-ruby:The above code runs on a large Sequel dataset with a PostgreSQL database.
TruffleRuby Native: steady and quite fast memory increase (40gb after 1h of CPU usage)
TruffuleRuby JVM: slower but steady memory increase (25gb after 1h of CPU usage)
In the screenshot above Ruby 3.1.2 compiled with jemalloc (pid 1006066) is also running with memory usage stabilized at around 1.2gb
So the same code is run with the 3 rubies, also with the same Gemfile.lock.
The text was updated successfully, but these errors were encountered: