Repository navigation
deps: adopt lower-allocation OTLP decoder stack - #176
Merged
Merged
Conversation
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.
Summary
Update the root OTel SDK from
26186ceto3366a33, composing the reviewed optimizations from casselc/otel #65 and #66 with the existing stock-codec/cache capabilities.The decoder reuses original scalar defaults and scans its seven fixed AnyValue fields without constructing a lazy filtered sequence. Profiling identified both as avoidable per-attribute allocation. These are ordinary library changes on stock Jolt; no compiler patch or new dependency is needed. Existing validation, error handling, optional codec/parser defaults and Durable confirmation rules stay unchanged.
Update the exact resolved-SDK source guard; retain all older negative controls. The minimal embedded profile is not repinned. Document why a global native-library override is inappropriate when testing root and minimal profiles with different native versions.
Validation
JOLT_CHDB_LIBunset so root and unchanged minimal fixtures use their own versioned assets. An earlier globally forced 26.9 override correctly failed the minimal fixture's 26.7.3 version guard; no source guard was relaxed.These application gates establish functional integration, not a throughput/tail gain. Decoder-only studies and the earlier scalar-only socket allocation comparison retain their original source scopes. Pre-existing typed benchmark provenance drift is tracked separately in #175; no historical measurements are relabeled by this repin.
Includes a changelog entry. No S3 performance, app packaging, or expanded persistence guarantee is claimed.