Skip to content

Conversation

@greged93
Copy link
Contributor

No description provided.

@codspeed-hq
Copy link

codspeed-hq bot commented Oct 16, 2025

CodSpeed Performance Report

Merging #367 will not alter performance

Comparing feat/update-metrics (92f819a) with main (68b4b43)

Summary

✅ 2 untouched

@greged93 greged93 changed the title Feat/update metrics feat: update metrics Oct 16, 2025
Copy link
Collaborator

@frisitano frisitano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, thanks! I left one comment inline regarding the sequencer metric implementation.

.as_mut()
.expect("signer must be present")
.sign_block(block.clone())?;
self.metric_handler.finish_block_building_recording();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we don't allow empty blocks then the finalize method below will return None. We should handle that case.

self
                    .sequencer
                    .as_mut()
                    .expect("sequencer must be present")
                    .finalize_payload_building(payload_id, &mut self.engine)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On second thought, maybe it was your intention to skip it such that we don't report metrics for empty blocks?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes the idea was only to record the actual block building duration for blocks that get added to the chain. I think we could however also have a metric for block building regardless of whether they get added to the chain, and also for the duration between 2 consecutive block added to the chain.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these could both be valuable to have

@frisitano frisitano merged commit 4b1d4d5 into main Oct 20, 2025
15 checks passed
@frisitano frisitano deleted the feat/update-metrics branch October 20, 2025 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants