We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We're creating a new empty payload (struct with 2 slices) on the heap each time one is needed.
Scenarios that create empty payloads include:
read()
Forest.Proofs()
And all payloads are deep copied upon read from the trie and update to the trie.
Reuse the same immutable empty payload instead of creating a new one each time.
Updates epic #1744
The text was updated successfully, but these errors were encountered:
I'm closing this issue because it doesn't seem like it would have enough impact to be worthwhile.
Sorry, something went wrong.
fxamacker
No branches or pull requests
Problem
We're creating a new empty payload (struct with 2 slices) on the heap each time one is needed.
Scenarios that create empty payloads include:
read()
creates new empty payloads when we try to read a non-existent pathForest.Proofs()
creates new empty payloads to generate proof for non-existent pathAnd all payloads are deep copied upon read from the trie and update to the trie.
The Proposed Solution
Reuse the same immutable empty payload instead of creating a new one each time.
Updates epic #1744
The text was updated successfully, but these errors were encountered: