-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
docs: memory profiling and OOM debugging tutorial #3819
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted filessee 578 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
a55a98e
to
b938364
Compare
what to do with this @Rjected ? |
bump @Rjected |
going to take a small chunk of time soon to finish this up and mark r4r |
@Rjected bump :) |
5bdd534
to
b847bb2
Compare
This still relevant @Rjected? If so let's merge or clsoe |
3cfb062
to
228e5e7
Compare
Should be useful, finished it up, let's merge |
This distills some of my previous attempts at fixing memory leaks in reth, so that memory leak debugging can be more accessible.
I aim to give an overview on the process one should go through when faced with a memory related bug or incident, as well as provide some useful intuition for rust and reth-specific debugging. This will be a more advanced tutorial, and will assume some knowledge about linux, memory, and how to set up reth, but should otherwise be a general document that anyone can learn from.