perf: Replace decodeOctal's call to parseInt on the tarInput hotpath#9
Merged
perf: Replace decodeOctal's call to parseInt on the tarInput hotpath#9
decodeOctal's call to parseInt on the tarInput hotpath#9Conversation
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
1 participant
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.
Every decoding of a Tar header requires us to read several octals. This hotpath contains an optional call to
parseInt(x, 16)which is slower than the alternative number format paths. For parity, this should avoid the call toparseInt, since the input is quite limited in its character set (only digits 0-7 are allowed).