Add caching of flash reads #184
Open
Conversation
This file contains 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
Gets fully invalidated on any writes, to minimise complexity, as the only read & write command is `picotool config` which wouldn't benefit from caching anyway
… matches cached data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add caching of flash reads from the device (#183), as the current metadata scans read from the same regions multiple times.
This provides a speedup to
picotool info -aon my 4 partition device from 5.7s to 1.6s, and speeds uppicotool infofrom 3.8s to 1.4s, so provides a good performance boost.Gets fully invalidated on any writes, to minimise complexity, as the only read & write command is
picotool configwhich wouldn't benefit from caching anyway. Also gets invalidated when usingpicotool save --verify, so you're not just verifying the cached data.