全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Reuse one CkbRpcClient across a loop instead of building one per item实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
Constructing a ckb_sdk CkbRpcClient (CkbRpcClient::with_builder) loads the TLS root store, about 6 ms of CPU each time. In Fiber's watchtower, building one per watched channel made a round over 11,496 channels take 93 to 115 s; building one client before the loop and passing &CkbRpcClient cut it to 5 to 7 s.
为什么重要: Building a new ckb_sdk CkbRpcClient for every item reloads the TLS root store each time, about 6 ms of CPU per item. Over 11,496 watched channels that stretched one watchtower round from 5 to 7 s to 93 to 115 s.
代码模式
推荐
let ckb_client = CkbRpcClient::with_builder(&rpc_url, |builder| { builder.timeout(CKB_RPC_TIMEOUT).no_proxy() }) (built once, before the for loop over watched channels)摘自提交,已缩短。
- 概念
- Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-03
- 最近改动
- 2026-11-03
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-03 · nervosnetwork/fiber · 这个项目的更多经验
更多关于CKB node, RPC and indexer
- get_live_cell may return "unknown" rather than "dead" for a spent output
- get_transaction returns an object with a null transaction for rejected and unknown txs
- send_transaction error -1111 (PoolRejectedRBF) is a conflict, not "already in pool"
引用这条经验
LusoCryptoLabs, "Reuse one CkbRpcClient across a loop instead of building one per item", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/reuse-one-ckbrpcclient-across-a-loop-instead-of-building-one, CC BY 4.0, last changed 2026-11-03.