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

Spiked external memory on network thread #6106

Closed
twoeths opened this issue Nov 14, 2023 · 2 comments
Closed

Spiked external memory on network thread #6106

twoeths opened this issue Nov 14, 2023 · 2 comments
Assignees
@twoeths
Labels
meta-bug Issues that identify a bug and require a fix. meta-investigate Issues found that require further investigation and may not have a specific resolution/fix scope-memory Issues to reduce and improve memory usage.

Comments

@twoeths
Copy link
Contributor

twoeths commented Nov 14, 2023

Describe the bug

Since at least v1.11.0, this happens randomly on network thread

Screenshot 2023-11-14 at 08 14 36

when that happened gc spiked a bit too

Screenshot 2023-11-14 at 08 15 12

Expected behavior

stable external memory on network thread

Steps to reproduce

No response

Additional context

No response

Operating system

Linux

Lodestar version or commit hash

v1.11.0
@twoeths twoeths added the meta-bug Issues that identify a bug and require a fix. label Nov 14, 2023
@twoeths twoeths changed the title Spked external memory on network thread Spiked external memory on network thread Nov 21, 2023
@twoeths twoeths self-assigned this Nov 28, 2023
@twoeths
Copy link
Contributor Author

twoeths commented Jan 12, 2024

still an issue with v1.13 and potentially v1.14

Screenshot 2024-01-12 at 18 24 48

need to double check after batchPublish option is available ChainSafe/js-libp2p-gossipsub#480

note that I don't see this issue with test mainnet nodes (nodes with no validator) so perhaps it's the issue in publish flow

@philknows philknows added scope-memory Issues to reduce and improve memory usage. meta-investigate Issues found that require further investigation and may not have a specific resolution/fix labels Jan 16, 2024
This was referenced Mar 22, 2024
Merged
Merged
@wemeetagain
Copy link
Member

closing as stale, no longer visible in metrics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@twoeths twoeths

Labels
meta-bug Issues that identify a bug and require a fix. meta-investigate Issues found that require further investigation and may not have a specific resolution/fix scope-memory Issues to reduce and improve memory usage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wemeetagain @twoeths @philknows