ethereum/go-ethereum

geth takes over an hour to start with a lot of keys in the keystore

Open

#16,874 建立於 2018年6月4日

在 GitHub 查看
 (22 留言) (0 反應) (0 負責人)Go (51,042 star) (21,913 fork)batch import
help wantedtype:feature

描述

Hi,

This has been going on for a long time but geth takes longer and longer to start up. Currently using the pre-compiled 1.8.10 on Linux 64-bit. Pretty beefy machine with 128GB of RAM, NVMe storage, 3 GHz Xeon w/ 8 cores / 16 threads.

My best guess is it's because we have a lot of keys since it's for a wallet provider.

Quick example from today showing timestamps between these 2 lines of geth output:

INFO [06-04|04:26:23] Maximum peer count ETH=25 LES=0 total=25 INFO [06-04|05:38:10] Starting peer-to-peer node instance=Geth/v1.8.10-stable-eae63c51/linux-amd64/go1.10.

貢獻者指南

技術棧
go
領域
backendperformance
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingEthereum basicsPerformance profiling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the keystore loading process in go ethereum, particularly in accounts/keystore/keystore.go. Profile startup using Go's pprof to identify bottlenecks. Explore options like parallelizing key decryption or lazy loading to reduce startup time with many keys.