docs: Modify examples to show best practices - reuse tracer #2709
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.
One of many with the goal of showcasing best practices in all examples maintained in this repo.
This PR shows how to re-use Tracer instead of repeatedly obtaining it from provider/global which involve at-least one atomic check and an Arc clone internally.
A simple benchmark was added to show the impact of Tracer creation.
If the direction is agreed, we need to review every examples and make sure they show best practices for all signals.