Skip to content

qualitative analysis of tcmalloc profiling data #1151

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

Open
Sashan opened this issue Apr 2, 2025 · 1 comment
Open

qualitative analysis of tcmalloc profiling data #1151

Sashan opened this issue Apr 2, 2025 · 1 comment

Comments

@Sashan
Copy link

Sashan commented Apr 2, 2025

both profilers (libtcmalloc and libmprofile) can collect detailed records about every call to alloc/free/realloc including a callstack.

the libtcmalloc allows to further fine-tune collection of heap profile samples. There are two env. variables:

  • HEAP_PROFILE_ALLOCATION_INTERVAL set to 1GB by default
  • HEAP_PROFILE_INUSE_INTERVAL set to 100MB by default.

details can be found here: https://gperftools.github.io/gperftools/heapprofile.html

one of the options for gperf is to generate analysis to .pdf file. attached file shows allocation graph for lhash_test. The The HEAP_PROFILE_ALLOCATION_INTERVAL and HEAP_PROFILE_INUSE_ALLOCATION were set to 5GB. Just one heap sample got collected during the test. It looks like we need to further tune intervals to collect more heap samples and analyze them.

@Sashan
Copy link
Author

Sashan commented Apr 2, 2025

test_lhash.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Pre-Refinement
Development

No branches or pull requests

1 participant