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

Brief explanations #15

Open
bobrik opened this issue Jul 4, 2013 · 1 comment
Open

Brief explanations #15

bobrik opened this issue Jul 4, 2013 · 1 comment

Comments

@bobrik
Copy link

bobrik commented Jul 4, 2013

I think it would be great to see a little section faq in README.md. Shallow size and retained size may be a good way to start.

Personally, I have dumps from 1 node.js process that are from 3mb to 67mb and chrome says they all 5.4mb. At the same time rss is increasing over time. I have no idea if I should worry about it or gc will do its work at some moment in the future.

@geekyme
Copy link

geekyme commented Aug 2, 2015

heapdump triggers a full GC prior to writing the snapshot to disk. That's why you will see your dump size being different from your rss. you should monitor your process over a long period to see whether there are any leaks.

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

No branches or pull requests

2 participants