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

Big NodeJS Event Loop Lag after v1.10.0 #5893

Closed
twoeths opened this issue Aug 16, 2023 · 4 comments
Closed

Big NodeJS Event Loop Lag after v1.10.0 #5893

twoeths opened this issue Aug 16, 2023 · 4 comments
Labels
meta-bug Issues that identify a bug and require a fix. prio-high Resolve issues as soon as possible.

Comments

@twoeths
Copy link
Contributor

twoeths commented Aug 16, 2023

Describe the bug

This is from a test mainnet node 10m chart

Screenshot 2023-08-16 at 14 25 32

Expected behavior

Should be close to stable mainnet node (v1.10.0)

Screenshot 2023-08-16 at 14 26 11

Steps to reproduce

No response

Additional context

No response

Operating system

Linux

Lodestar version or commit hash

v1.10.0/7546292
@twoeths twoeths added the meta-bug Issues that identify a bug and require a fix. label Aug 16, 2023
@twoeths
Copy link
Contributor Author

twoeths commented Aug 16, 2023

this is respective to "Prometheus scrape duration"

Screenshot 2023-08-16 at 15 16 48

vs v1.10.0

Screenshot 2023-08-16 at 15 17 13

@twoeths
Copy link
Contributor Author

twoeths commented Aug 16, 2023

not sure how to deal with this, stable mainnet node has way less gossipsub traffic (due to low mesh peers) that's why it's not lag as unstable

@philknows philknows added the prio-high Resolve issues as soon as possible. label Aug 16, 2023
@twoeths
Copy link
Contributor Author

twoeths commented Aug 16, 2023

looking for #2115 to help mitigate/resolve this issue

@twoeths
Copy link
Contributor Author

twoeths commented Aug 24, 2023

Screenshot 2023-08-24 at 15 41 52

this is resolved after we enable network thread

@twoeths twoeths closed this as completed Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta-bug Issues that identify a bug and require a fix. prio-high Resolve issues as soon as possible.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@twoeths @philknows