twoeths

Results 315 comments of twoeths

there is also big scrape duration and weird event lag issues

some more logs for this ``` 2025-06-05 23:58:47.530 | Jun-05 16:58:47.530[chain] warn: SyncContributionAndProofPool.getAggregate: no contributions for root slot=11859891, root=0x6f7f9e41d60c4bd4d763259672fbcf0d2e0b38925c4342354b428afaec30a216, availableRoots=0x437f572e8952b23d875257813edbadb4bff6caed3aa8eb589ef0e52bd127da13,0x6f7f9e41d60c4bd4d763259672fbcf0d2e0b38925c4342354b428afaec30a216 |   -- | -- | --   |   | 2025-06-05 23:02:35.287...

the change makes a lot of sense to me. For lodestar on holesky, it takes ~530ms for `hash_tree_root` on epoch transition with wasm sha256 and going to be 130ms -...

we archive states at every finalized epoch which is not correct ``` 2025-10-13 18:12:57.067 | Oct-13 11:12:57.067[chain] verbose: Archived state completed finalizedEpoch=47239, minEpoch=46080, storedStateSlots=1474560,1507328,1511616, statesSlotsToDelete=1511616 |   -- | -- |...

looks like `db.stateArchive.lastKey()` returned the wrong value same to first time starting beacon-node ``` 2025-10-13 19:36:17.713 | Oct-13 12:36:17.713[] verbose: Found the last archived state slot=39936, size=145.10 MB |   --...

looks like `reverse` option was not respected

detailed log of a finalized epoch processing ``` Oct-13 10:14:48.033[chain] ^[[36mverbose^[[39m: Start processing finalized checkpoint epoch=47230, rootHex=0x2958646b9763ed911998d336f76a091bcf2d4b24aaa58e2dc986441846dc2bd8 Oct-13 10:14:48.058[chain] ^[[36mverbose^[[39m: Migrated blocks from hot DB to cold DB fromSlot=1511360, toSlot=1511329,...

after #8529 there is still a performance issue with `const lastStoredSlot = await this.db.stateArchive.lastKey();` which blocks the main thread @wemeetagain

update: deployed to another lg1k node and it said `const lastStoredSlot = await this.db.stateArchive.lastKey();` is only blocked for 2.6s - still not great but way less than the above beacon...

> @twoeths what do you think about moving the "Aggregated Attestation Pool" row a bit further down in the dashboard? sounds good to me @nflaig