usage: avoid creating unnecessary instance periods#126
Merged
Conversation
b014c10 to
01f98fb
Compare
This is important. Without this, the code can generate many instance periods and it ends up consuming a significant part of the total CPU time.
01f98fb to
b3fe82b
Compare
unleashed
approved these changes
Sep 10, 2019
Contributor
Author
|
bors r=@unleashed |
bors Bot
added a commit
that referenced
this pull request
Sep 10, 2019
126: usage: avoid creating unnecessary instance periods r=unleashed a=davidor This PR introduces a performance optimization in the part of the code that calculates the current usage. This is important for users with lots of metrics and limits. Without this, the code can generate many instance periods and it ends up consuming a significant part of the total CPU time. Co-authored-by: David Ortiz <z.david.ortiz@gmail.com>
Contributor
Build succeeded |
Contributor
Author
|
For the record, I used stackprof to measure the performance impact of this change. I called The method optimized in this PR is Notice that the % here will vary a lot depending on the number of metrics, limits, etc. of the service under test. Before After |
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.
This PR introduces a performance optimization in the part of the code that calculates the current usage.
This is important for users with lots of metrics and limits. Without this, the code can generate many instance periods and it ends up consuming a significant part of the total CPU time.