Chaintip performance analysis

no concrete action planned atm, many ideas to be tested, this one is to track what have been attempted.

ongoing experiments based on the assumption:

reset DB state to latest of static files
clean pagecache
advance and profile a few blocks

build/bin/integration stage_exec --datadir $DATADIR --chain mainnet --reset
sync && sudo purge
build/bin/integration stage_exec --datadir $DATADIR --chain mainnet --sync.mode.chaintip --block=$STOPBLOCK --$PROFILEFLAGS

initial CPU profiling shows decompressor.nextPos() as a hot path, but it looks more like a red herring.

attempted to do a couple of microoptimizations to it, but nothing significant. I'll look into usage patterns of callers to better understand what can be done.

note to myself: use -focus "ExecBlockV3" into profiling to isolate the noise even on 1 block profiling.

yperbasis added Imp2 as Importance

about nextPos(): it may be red because it’s actually where “page cache miss” happening. “.data” field usage.

You can read file twice: and see difference in profiler picture. Can use: “erigon snapshots uncompress file.kv > /dev/null”

closing because no activity

Navigation Menu

Repository navigation

Chaintip performance analysis #17272

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Chaintip performance analysis #17272

Description

Activity

wmitsuda commented on Sep 29, 2025

wmitsuda commented on Sep 29, 2025

wmitsuda commented on Sep 29, 2025

VBulikov commented on Oct 2, 2025

AskAlexSharov commented on Oct 2, 2025

AskAlexSharov commented on May 12, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions