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.
perf(state): eliminate speculative trie allocation storm via double-c… #2286
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
base: develop
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
perf(state): eliminate speculative trie allocation storm via double-c… #2286
Changes from all commits
feae2bae778a795f03a2c1d29f4dFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure on line 596 in core/state/reader.go
Check failure on line 596 in core/state/reader.go
Check failure on line 596 in core/state/reader.go
Check failure on line 596 in core/state/reader.go
Check failure on line 596 in core/state/reader.go
Check failure on line 610 in core/state/reader.go
Check failure on line 610 in core/state/reader.go
Check failure on line 610 in core/state/reader.go
Check failure on line 610 in core/state/reader.go
Check failure on line 610 in core/state/reader.go
Check failure on line 636 in core/state/reader.go
Check failure on line 636 in core/state/reader.go
Check failure on line 636 in core/state/reader.go
Check failure on line 636 in core/state/reader.go
Check failure on line 636 in core/state/reader.go
Check failure on line 647 in core/state/reader.go
Check failure on line 647 in core/state/reader.go
Check failure on line 647 in core/state/reader.go
Check failure on line 647 in core/state/reader.go
Check failure on line 647 in core/state/reader.go
Check failure on line 676 in core/state/reader.go
Check failure on line 676 in core/state/reader.go
Check failure on line 676 in core/state/reader.go
Check failure on line 676 in core/state/reader.go
Check failure on line 676 in core/state/reader.go
Check failure on line 682 in core/state/reader.go
Check failure on line 682 in core/state/reader.go
Check failure on line 682 in core/state/reader.go
Check failure on line 682 in core/state/reader.go
Check failure on line 682 in core/state/reader.go
Check failure on line 703 in core/state/reader.go
Check failure on line 703 in core/state/reader.go
Check failure on line 703 in core/state/reader.go
Check failure on line 703 in core/state/reader.go
Check failure on line 703 in core/state/reader.go
Uh oh!
There was an error while loading. Please reload this page.