-
Notifications
You must be signed in to change notification settings - Fork 584
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
network: Investigate high memory consumption for long-running node #4927
Comments
Triaging local logs
|
A similar behavior can be seen with libp2p backend:
Considering that the node was not terminated after ~90 days by OOM killer, and litep2p backend consumes less memory than libp2p I would treat this issue with a lower priority for now. |
lexnv
changed the title
network/litep2p: Investigate high memory consumption for long-running node
network: Investigate high memory consumption for long-running node
Jul 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 Kusama nodes were started on 23th April and left running.
The commit was based on a2a049d, from branch:
These are the same nodes as: #4925
Extracted metrics: metrics.txt
The long-running nodes are roughly consuming
36253.95 Mb
and31372.94 Mb
compared to a freshly started node4540.62 Mb
Metrics
CPU metric usage is consumed almost entirely by the network-worker and "libp2p-node" metrics.
(note this is using the litep2p backend).
The "libp2p" metric has almost 38/40 running tasks running at a time.
Total network inbound: 2.6 TiB
Total network outbound 806 GiB
Node oscillated between 0 and 1 syncing peer.
Mpsc_import_notification_stream is the only channel with 160 messages queued (dashboard might be wrong).
Chain_sync and Network_worker are sending messages, with occasional peer-set, network-gossip and transactions-handler-sync.
The text was updated successfully, but these errors were encountered: