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.

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

Max heap size does not match the actual maximum allocated memory #121

Open
fulmicoton opened this issue Apr 17, 2024 · 0 comments
Open

Max heap size does not match the actual maximum allocated memory #121

fulmicoton opened this issue Apr 17, 2024 · 0 comments

Comments

@fulmicoton
Copy link

fulmicoton commented Apr 17, 2024

(thank you for the amazing project!)

I am running bytehound on a multithreaded rust server. There are no child process.
While running, I see resident memory using top reaching 8GB. This is not off-heap data: jemalloc's allocated memory (exposed via an endpoint on my server) also reaches close to 8GB.

However, bytehound reports suggests a peak of around 1GB.
Where could the discrepancy come from?

Does bytehound drops allocation if it cannot keep up with the logging?
Is there a way to do sampling over the allocations?

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

No branches or pull requests

1 participant