encoding/mvt: use protoscan for unmarshalling#57
Merged
Conversation
benchmark old ns/op new ns/op delta BenchmarkUnmarshal-12 367590 246198 -33.02% benchmark old allocs new allocs delta BenchmarkUnmarshal-12 6629 2476 -62.65% benchmark old bytes new bytes delta BenchmarkUnmarshal-12 372954 211681 -43.24%
d98aadc to
cc0f895
Compare
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
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.
Vector Tiles have an encoding for the geometry. This causes an intermediate state were the protobuf is unpacked into a
[]uint32and then converted into theorb.Geometrytypes. This intermediate step can be removed by using a low lever decoder like protoscanThe behavior is the same, but the performance is substantially better: