Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
josepot
approved these changes
Mar 18, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously, we were keeping every block for up to 1 hour. However, with the new block time (2s) it increases past a point where the Block explorer starts lagging.
This PR changes the limit to height: Every block will stay in memory until there are 600 on top of it (so it's the equivalent of what we had before)
There's a further optimisation of virtualising the list, but this adds more challenges (specially for the split Block + Events view in wide screen and stacked in narrow screen), double scrolls, we lose Ctrl+F accessibility, etc. I started working on this, but I dropped it for all these reasons.... might re-pick it later if we have bandwidth.