twoeths

> Performance is inconsistent because we only re-hash new nodes in the tree since the last hashTreeRoot. > If there aren't many new nodes, it takes less time. > If...

this is due to our `hash` implementation in as-sha256 https://github.com/ChainSafe/as-sha256/pull/45, I don't see anything that can be improved in `ssz` or `persistent-merkle-tree` regarding this.

> @tuyennhv According to a CPU profile are the intToBytes, bytesToInt functions part of a critically hot path worth optimizing? no this is not critical, these functions just use BigInt...

It's still an issue in Goerli from what I see, this is from a stable node (5 first days with v1.0.0 and 2 last days with v1.1.0, they are the...

Some different gossipsub metrics I notice after 6h-7h (in a 12h timeframe): - Heartbeat is way faster - Score functions are called less - We send out way less RPC...

root cause could be https://github.com/ChainSafe/lodestar/pull/4427 v1.0.0 v1.1.0 rc.0

tested with `v1.3.0/080b73b` on a ctvpss node 1st time: - Remove `peerstore`, node gets to targetPeers in 22 minutes - Restart node, node gets to targetPeers in 9 minutes -...

not an issue anymore since v1.2.0, below is 10m rate interval on the stable 1k node:

the current gh page works well until now

somehow there is a gap between new deposit index and old deposit index, this is strange because we always based on highest deposit event block number before fetching deposit events...