[QA] Load lazy fields on init in the background #3803
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.
📜 Description
Lazy fields in SentryOptions are now loaded on init in the background
💡 Motivation and Context
Instead of loading the options fields backed by LazyEvaluator when needed, we do it in the background as soon as we can. When the SDK will need these fields, they will be already cached and ready to use
This improved init() by ~5-15ms in profileable builds
💚 How did you test it?
📝 Checklist
sendDefaultPII
is enabled.🔮 Next steps