-
Notifications
You must be signed in to change notification settings - Fork 649
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
Resolve 1371: sorting of public_keys is inefficient #1401
Conversation
…_transaction_signatures
3826ef3
to
bbb8730
Compare
Rebased and adapted new test case from #1384 |
I updated title of this PR to more descriptive since it helps when viewing PR list. |
It turns out that the check for irrelevant signatures relies on key ordering as well. Will have to refactor. |
aeea794
to
a3558aa
Compare
Test results so far indicate that this change does not result in significant speedup for replay, resync or resync with force-validate.
(Resync was done at different times of day, fluctuations due to network conditions are to be expected.) |
Measurements have shown this to be a non-issue. Closing. |
Implemented full solution for #1371
Also cherry-picked some changes from #1360