Performance comparison

CL node stats

Enabled

Disabled

Results

When enabled, CPU usage peaks at over 2.5 and is quite erratic, mem usage approaching 2.5GB When disabled, CPU peaks at just over 1.0 with occasional spikes, memory spike to 2GB but mostly stays at 1.25GB

DB node stats

Enabled

Disabled

Results

When enabled, CPU peaks at around 1.0, with early RAM spikes to 1 GB, but doesn't go much higher than 1GB overall When disabled, CPU peaks just over 0.3, with no RAM spikes, but overall higher usage of 1.25

Missed logs

Enabled

Disabled

Results

No stats are reported when the recoverer is disabled

github-actions[bot] commented 6 days ago

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

#added For any new functionality added.
#breaking_change For any functionality that requires manual action for the node to boot.
#bugfix For bug fixes.
#changed For any change to the existing functionality.
#db_update For any feature that introduces updates to database schema.
#deprecation_notice For any upcoming deprecation functionality.
#internal For changesets that need to be excluded from the final changelog.
#nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
#removed For any functionality/config that is removed.
#updated For any functionality that is updated.
#wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.