perf(core): [SDK Overhead Reduction 8] Reduce context serialization allocations#5599
Draft
adinauer wants to merge 1 commit into
Draft
Conversation
Use sorted key arrays when serializing contexts to avoid allocating an ArrayList for each serialization. This preserves deterministic key ordering while keeping the snapshot representation smaller. Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Jun 23, 2026
Merged
📲 Install BuildsAndroid
|
Contributor
Performance metrics 🚀
|
This was referenced Jun 23, 2026
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.
PR Stack (SDK Overhead Reduction)
📜 Description
Uses sorted
String[]key snapshots when serializingContextsandMonitorContexts.This replaces
Collections.list(keys())plusCollections.sort()withkeySet().toArray(...)plusArrays.sort(...).💡 Motivation and Context
Context serialization needs deterministic alphabetical key ordering, but the previous implementation allocated an
ArrayListwrapper for each serialization. A plain key array preserves the same ordering behavior while avoiding the extra list allocation.💚 How did you test it?
./gradlew :sentry:test --tests io.sentry.protocol.ContextsSerializationTest --tests io.sentry.MonitorContextsTest./gradlew spotlessApply apiDump📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
#skip-changelog