Description
While checkpoint syncing glamsterdam-devnet-3 in a period of long non-finality, I noticed we prime the proposer shuffling cache for the chains head epoch. For devnet-3 this took us roughly 3.5 minutes because we had to transition through a bunch of epochs. During that time we were blocked from doing anything. We should probably disable priming the proposer shuffling cache during checkpoint sync.
Summary of logs from Claude
05:58:47.779 — "Parent state is not advanced" block_slot: 15776, state_slot: 15775
... 3 min 28 sec of NOTHING (just slot timers) ...
06:02:15.509 — "Priming proposer shuffling cache" epoch: 1258
06:02:15.512 — Cached state at slot 15776
06:02:15.555 — Block 15776 imported
06:02:15.556 — "Parent state is not advanced" block_slot: 15777, state_slot: 15776
... 3 min 26 sec of NOTHING ...
06:05:41.992 — "Priming proposer shuffling cache" epoch: 1259
06:05:41.995 — Block 15777 imported
06:05:41.999 — Block 15778 imported (instant)
06:05:42.002 — Block 15779 imported (instant)
06:05:42.004 — Block 15780 imported (instant)
06:05:42.007 — Block 15781 imported (instant)
06:05:42.009 — Block 15782 imported (instant)
Description
While checkpoint syncing glamsterdam-devnet-3 in a period of long non-finality, I noticed we prime the proposer shuffling cache for the chains head epoch. For devnet-3 this took us roughly 3.5 minutes because we had to transition through a bunch of epochs. During that time we were blocked from doing anything. We should probably disable priming the proposer shuffling cache during checkpoint sync.
Summary of logs from Claude