chore(sig): define signature metadata statically #4237
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rscampos
force-pushed
the
chore_signature_metadata_golang
branch
2 times, most recently
from
4e9c20c to
a1ceedd
Compare
Compared to the previous method of defining metadata, using static signature metadata declaration has been shown to improve performance by approximately 20% to 30%, according to benchmark results.
rscampos
force-pushed
the
chore_signature_metadata_golang
branch
from
a1ceedd to
5ddbc4d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Explain what the PR does
5ddbc4d core(test): static sig metadata declaration
4a5dbbb chore: static sig metadata declaration
4a5dbbb chore: static sig metadata declaration
2. Explain how to test it
3. Other comments
The results of the benchmark is explained in this PR #4223