solana-labs/solana

validator uses more memory than expected when metrics are enabled

Open

#24,319 创建于 2022年4月13日

在 GitHub 查看
 (26 评论) (0 反应) (1 负责人)Rust (12,651 star) (3,950 fork)batch import
do-not-closegood first issue

描述

Problem

80GB difference between RUST_LOG=solana=info and RUST_LOG=solana=warn for RPC nodes.

Proposed Solution

Relevant question.. is the channel that the metrics are sending to really large? Could there be some large amount of outstanding sends which each is taking some memory and state?

Debug and find why. Possibly reduce the occurrence of spammy metrics.

贡献者指南

技术栈
rust
领域
performanceobservability
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Rust programmingbasic understanding of Solana validator architecture
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Investigate the memory increase when metrics are enabled. Look at the metrics sending channel in the Solana validator code (likely in `validator/src/` or `metrics/`). Profile memory usage with tools like `heaptrack` or `valgrind` to identify where the excess memory is allocated. Check if outstanding sends in the metrics channel are accumulating. Reduce spammy metrics by filtering or batching. Review comments from the issue for additional hints.