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

Investigate resident set vs heap total memory difference #3510

Open
1 of 2 tasks
dapplion opened this issue Dec 10, 2021 · 1 comment
Open
1 of 2 tasks

Investigate resident set vs heap total memory difference #3510

dapplion opened this issue Dec 10, 2021 · 1 comment
Labels
meta-investigate Issues found that require further investigation and may not have a specific resolution/fix prio-medium Resolve this some time soon (tm). scope-memory Issues to reduce and improve memory usage.

Comments

@dapplion
Copy link
Contributor

Lodestar nodes show a significant difference between the process resident set or total process memory and the total heap size. As far as I'm concerned, there's no other large memory item that could justify a 500MB difference

Screenshot from 2021-12-10 18-34-46

This issue is to track research into what could cause this difference:

  • Worker threads: I've disabled all workers (second part of the chart above) and while the total process size is slightly lower the difference is roughly the same
  • ??
@dapplion dapplion added the scope-memory Issues to reduce and improve memory usage. label Dec 10, 2021
@dapplion dapplion added the prio-medium Resolve this some time soon (tm). label Feb 4, 2022
@philknows
Copy link
Member

It might be array buffer backing stores or native code package allocation? How do we debug this? Need to investigate that first. Core dumps?

@philknows philknows added the meta-investigate Issues found that require further investigation and may not have a specific resolution/fix label Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta-investigate Issues found that require further investigation and may not have a specific resolution/fix prio-medium Resolve this some time soon (tm). scope-memory Issues to reduce and improve memory usage.
Projects
None yet
Development

No branches or pull requests

4 participants