Serialize tags/metrics in a single pass #1416
Merged
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.
Tags and metrics were initially serialized in a single pass, and the count was back-patched at the end. This caused issues because the MessagePack map header has a variable size, so in some cases I ended up not allocating enough space. This was fixed by switching to a two-pass algorithm, with a performance hit: #996
I just realized that there's actually an API to write a fixed-size header, so I'm switching back to a single-pass algorithm. The existing unit test
TagsListTests.Serialization
verifies that it does not introduce any regression (I confirmed beforehand that the test still fails if I useMessagePackBinary.WriteMapHeader
instead ofMessagePackBinary.WriteMapHeaderForceMap32Block
).