Skip to content

Conversation

@georgehao
Copy link
Member

No description provided.

@georgehao georgehao changed the title Improve sequencer metrics feat: improve sequencer metrics Dec 18, 2025
@codspeed-hq
Copy link

codspeed-hq bot commented Dec 18, 2025

Merging this PR will not alter performance

✅ 2 untouched benchmarks


Comparing feat/improve_sequencer_metrics (de0274d) with main (c3ec1a2)1

Open in CodSpeed

Footnotes

  1. No successful run was found on main (dab4f84) during the generation of this report, so c3ec1a2 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

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.

I've added some comments inline. On a high level I think we should record the following metrics:

  • block_building_duration: the time it takes to build a non-empty block
  • empty_block_building_duration: the time it takes to build an empty block
  • consecutive_block_interval: the time between two consecutive blocks that are added to the canonical chain.

I'm not sure if you had a different idea about these metrics to please let me know if I have misunderstood something.

@georgehao
Copy link
Member Author

georgehao commented Jan 7, 2026

  • block_building_duration: the time it takes to build a non-empty block
  • empty_block_building_duration: the time it takes to build an empty block

Oh, I understand it is that:

if I want to check the block building duration, I will check the whole block building duration, then check the no-empty block building duration, then I will get the conclusion for it ( because the empty block building will always have a constant value, no sense to display this alone, and can calculate it from the all_block_building_duration and block_building_duration)

What do you think?

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.

Added a comment inline. I think the description you provided does not match the code.

@georgehao georgehao force-pushed the feat/improve_sequencer_metrics branch from 4107508 to d941f8b Compare January 12, 2026 08:57
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.

I think this solution doesn't work as expected. Please let me know if I made a mistake in my understanding.

@frisitano frisitano merged commit b77ae04 into main Jan 30, 2026
17 of 18 checks passed
@frisitano frisitano deleted the feat/improve_sequencer_metrics branch January 30, 2026 13:07
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