twoeths

I deployed #7043 to beta, metrics look good to me, all are comparable to unstable

tested with finalized state slot 1885504 of holesky ```typescript const chainForkConfig = createChainForkConfig(holeskyChainConfig); const now = Date.now(); const wsState = getStateTypeFromBytes(chainForkConfig, stateBytes).deserializeToViewDU(stateBytes); console.log("@@@ loaded state", wsState.slot, Date.now() - now, "ms");...

``` Aug-26 06:40:22.054[] ^[[32minfo^[[39m: Lodestar network=holesky, version=v1.21.0/te/shared_buffer_sync_pubkeys_2/93e2c66, commit=93e2c66c4d93b5a145bcaf183a0f28982508046b Aug-26 06:40:22.199[] ^[[32minfo^[[39m: Connected to LevelDB database path=/home/devops/beacon/chain-db Aug-26 06:40:46.360[] ^[[33mwarn^[[39m: Forced syncing from checkpoint even though db state is within weak...

posting some great metrics (the test mainnet node) captured from `feat1` - 6h rate interval - Prepare Next Epoch time is ~600ms faster than beta/unstable and ~500ms faster on mainnet...

- "till become head" is ~30ms faster than stable on mainnet, somehow it's the same to beta mainnet node - it's ~90ms faster on holesky (both beta + mainnet) -...

a side effect from this branch is "Process block commit step avg time" is usually higher than `stable` (

closing in favor of #7171

The block process time is not bad in the above time range it's likely most of the time was spent for loading block from db + deserialize it + wait...

> Average block processed time is 8.6s/23 = 374ms which is too much. Normally it should be

this is `getPreState()` time on the feat4 mainnet node with PR #7033 it was reduced from 13.2s (as in the`Description`) to 7.29s which is likely the worse case scenario, this...