mit-pdos/noria

Dynamic load profiling

Open

#90 建立於 2018年9月19日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Rust (4,576 star) (229 fork)batch import
enhancementhelp wantedm-debugging

描述

It'd be really cool if the system kept stats about how "busy" different parts of the graphs were. For example, how many records they're processing per second or how long they spend idle between every time they're woken up. This might help to identify performance regressions and opportunities for optimization, but could also have a wider impact by allowing the controller to re-shard or replicate nodes in response to increase/decreased load.

貢獻者指南

技術棧
rust
領域
performance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Rust programmingDataflow system conceptsPerformance profiling basicsNoria architecture knowledge
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
To implement this feature, first study the Noria architecture, especially the graph execution engine and handling of internal state. Explore existing profiling infrastructure in the codebase (e.g., metrics or logging) and propose a set of metrics to collect. Since no prior discussion exists, open a design issue or ask maintainers for guidance on preferred approach and integration points. The main challenge is deciding where to insert profiling hooks without significant performance overhead.