Skip to content

refactor: use ElementIdGenerator for id generation in benchmarks#21

Merged
mweidner037 merged 5 commits intomweidner037:masterfrom
EastSun5566:chore/use-elementIdGenerator-in-benchmarks
Jan 14, 2026
Merged

refactor: use ElementIdGenerator for id generation in benchmarks#21
mweidner037 merged 5 commits intomweidner037:masterfrom
EastSun5566:chore/use-elementIdGenerator-in-benchmarks

Conversation

@EastSun5566
Copy link
Copy Markdown
Contributor

Closed #16 . Also bumped the Actions version and added build and benchmark tests.

Copy link
Copy Markdown
Owner

@mweidner037 mweidner037 left a comment

Choose a reason for hiding this comment

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

Thank you, and sorry for the delay! One small request, and then I will regenerate benchmark_results.md on the same machine as before.

Looks like this made sending faster due to the internal counter state instead of calling maxCounter. Though I'm not sure why saving and loading is also faster - laptop variability?
@mweidner037 mweidner037 merged commit f3ecff7 into mweidner037:master Jan 14, 2026
1 check passed
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.

Use ElementIdGenerator in benchmarks

2 participants