Skip to content
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

code: remove accountTrieCache and storageTrieCache #1949

Merged
merged 2 commits into from
Oct 30, 2023

Conversation

brilliant-lx
Copy link
Collaborator

Description

accountTrieCache and storageTrieCache were introduced in this PR: #257, which is to improve performance. Actually the performance gain is quite limitted, as there is already dirty and clean cache for trie node.
And after big merge, these 2 cache can not be used when PBSS is enabled. So remove these code to simplify the logic.

Rationale

NA

Example

NA

Changes

NA

accountTrieCache and storageTrieCache were introduced in this PR:
bnb-chain#257, which is to improve performance.
Actually the performance gain is quite limitted, as there is already dirty
and clean cache for trie node.
And after big merge, these 2 cache can not be used when PBSS is enabled.
So remove these code to simplify the logic.
core/state/database.go Outdated Show resolved Hide resolved
@joeylichang
Copy link
Contributor

revert trie commited flag in other PR ?

@brilliant-lx brilliant-lx merged commit 3bf998f into bnb-chain:develop Oct 30, 2023
5 checks passed
whw188 pushed a commit to tylerteea/mev-bsc that referenced this pull request Dec 6, 2023
accountTrieCache and storageTrieCache were introduced in this PR:
bnb-chain#257, which is to improve performance.
Actually the performance gain is quite limited, as there is already dirty
and clean cache for trie node.
And after big merge, these 2 cache can not be used when PBSS is enabled.
So remove these code to simplify the logic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants