-
Notifications
You must be signed in to change notification settings - Fork 38.7k
Add Benchmark to test input de-duplication worst case #14400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Benchmark to test input de-duplication worst case #14400
Conversation
|
Concept ACK |
90b3b22 to
e1ed29f
Compare
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
e1ed29f to
7bd1165
Compare
b9ee939 to
bb5baab
Compare
|
@MarcoFalke rebased, clang-formatted, etc. failure is unrelated to this PR now (one of the PBST tests) |
maflcko
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Squash the fixup, so all commits compile?
bb5baab to
4a55f55
Compare
Fix nits replace utiltime?
4a55f55 to
e4eee7d
Compare
|
should be ready to merge now, pending integration tests. Thanks! |
|
utACK e4eee7d
|
… case e4eee7d Add Benchmark to test input de-duplication worst case (Jeremy Rubin) Pull request description: Because there are now 2PRs referencing this benchmark commit, we may as well add it independently as it is worth landing the benchmark even if neither patch is accepted. bitcoin#14397 bitcoin#14387 Tree-SHA512: 4d947323c02297b0d8f5871f9e7cc42488c0e1792a8b10dc174a25f4dd53da8146fd276949a5dbacf4083f0c6a7235cb6f21a8bc35caa499bc2508f8a048b987
Because there are now 2PRs referencing this benchmark commit, we may as well add it independently as it is worth landing the benchmark even if neither patch is accepted.
#14397
#14387