Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document memory profiling for neard #11389

Closed
nagisa opened this issue May 24, 2024 · 0 comments · Fixed by #11393
Closed

Document memory profiling for neard #11389

nagisa opened this issue May 24, 2024 · 0 comments · Fixed by #11393
Labels
C-docs Category: documentation, including rustdoc, nomicon, and docs.nearprotocol.com

Comments

@nagisa
Copy link
Collaborator

nagisa commented May 24, 2024

Turns out that getting neard run with a memory profiler is a not very easy! I had some success with bytehound. We should document the process and choices so that other people need not to rediscover this all themselves next time memory profiling comes up.
@nagisa nagisa added the C-docs Category: documentation, including rustdoc, nomicon, and docs.nearprotocol.com label May 24, 2024
@nagisa nagisa mentioned this issue May 27, 2024
Merged
github-merge-queue bot pushed a commit that referenced this issue May 29, 2024
@nagisa
doc: add a page on profiling (#11393)
ccfbdeb 
This includes both the somewhat well known information on how to use
perf as well as text on bytehound, which is the only tool that seems to
work for memory profiling neard.

Fixes #11389
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-docs Category: documentation, including rustdoc, nomicon, and docs.nearprotocol.com
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

doc: add a page on profiling nagisa/nearcore
1 participant
@nagisa