ipfs/kubo

Block cache lock contention

Open

#6,934 建立於 2020年2月26日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
exp/experthelp wantedkind/enhancementstatus/readytopic/perf

描述

There is quite a bit of lock contention in the block cache. On the gateways, out of 32 walk threads:

  • 13 were waiting on the disk.
  • 19 were blocked on the cache.
    • 10 trying to add blocks
    • 9 trying to get them.

We're currently using github.com/hashicorp/golang-lru.

貢獻者指南

技術棧
go
領域
performance
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Goconcurrencycachinglock contention
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate the lock contention in the block cache by profiling the kubod daemon. Focus on the usage of github.com/hashicorp/golang lru and explore alternative cache implementations or lock free data structures. Analyze the code in the block cache module (likely in the core or blocks package) to identify where Add and Get calls are heavily contested.