RUMM-2753: Improve SDK performance a bit#1153
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/sdkv2 #1153 +/- ##
=================================================
- Coverage 82.38% 82.30% -0.08%
=================================================
Files 352 353 +1
Lines 11756 11796 +40
Branches 2006 2007 +1
=================================================
+ Hits 9685 9708 +23
- Misses 1451 1464 +13
- Partials 620 624 +4
🚀 New features to boost your workflow:
|
mariusc83
requested changes
Nov 23, 2022
mariusc83
approved these changes
Nov 23, 2022
xgouchet
approved these changes
Nov 23, 2022
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.
What does this PR do?
This change does the following:
lazy, because it shouldn't be changed during the app lifetime anyway.PUBLICATIONmode is used forlazywhich is usingcompareAndSetvs synchronisation by default (see docs for the difference), which should be a bit faster.SdkCoregetstimeproperty in order to avoid pulling the wholeDatadogContextwhen only time piece is needed. I had to implementNoOpSdkCoreby hand because of that, because no-op generation doesn't support properties and anyway if it would it cannot know what default value ofTimeInfoto create.CoreFeatureis completely removed from theSessionReplayfeature.Review checklist (to be filled by reviewers)