-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PROF-10688] Remove a looping allocation when updating threads #135
Merged
Conversation
This file contains 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
r1viollet
commented
Oct 1, 2024
🔧 Report generated by pr-comment-scanbuild Scan-Build Report
Bug Summary
Reports
|
r1viollet
commented
Oct 1, 2024
jbachorik
reviewed
Oct 7, 2024
r1viollet
commented
Oct 9, 2024
r1viollet
changed the title
Remove a looping allocation when updating threads
[PROF-10688] Remove a looping allocation when updating threads
Oct 9, 2024
jbachorik
approved these changes
Oct 11, 2024
5 tasks
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?:
Remove a looping allocation when updating threads
Motivation:
I do not have numbers that would justify that this is important.
Additional Notes:
For long thread names we would still have an allocation in string creation, however we previously had 2 (as we copied the C string to the std::string)
How to test the change?:
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!