Currently, trie keys generation will gather all transactions data and generate a single large batch of trie keys at once.
However, there are already mechanisms implemented in Besu to preload those trie keys in a background thread during block processing.
This PR generates the different triekeys in the background in order to have a maximum of triekeys already calculated at the end of the block
Fixed Issue(s)
Thanks for sending a pull request! Have you done the following?
PR description
Currently, trie keys generation will gather all transactions data and generate a single large batch of trie keys at once. However, there are already mechanisms implemented in Besu to preload those trie keys in a background thread during block processing.
This PR generates the different triekeys in the background in order to have a maximum of triekeys already calculated at the end of the block
Fixed Issue(s)
Thanks for sending a pull request! Have you done the following?
doc-change-required
label to this PR if updates are required.Locally, you can run these tests to catch failures early:
./gradlew build
./gradlew acceptanceTest
./gradlew integrationTest
./gradlew ethereum:referenceTests:referenceTests