catalog/descs: remove an allocation due to logging #89260
Closed
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
This commit removes an allocation that we incurred due to a logging message - constructing the log message wasn't free in this case, so we hide it behind an "expensive logging enabled" check. ``` name old time/op new time/op delta SQL/MultinodeCockroach/Upsert/count=1000-24 25.5ms ± 4% 24.1ms ± 5% -5.15% (p=0.000 n=10+10) name old alloc/op new alloc/op delta SQL/MultinodeCockroach/Upsert/count=1000-24 10.7MB ±13% 10.6MB ±18% ~ (p=0.497 n=9+10) name old allocs/op new allocs/op delta SQL/MultinodeCockroach/Upsert/count=1000-24 79.1k ± 6% 73.2k ± 6% -7.50% (p=0.007 n=10+10) ``` Release note: None
|
This change is |
|
This will be fixed and then some by #88614 I believe. Sprucing it up now. |
|
Ack, thanks. |
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 commit removes an allocation that we incurred due to a logging message - constructing the log message wasn't free in this case, so we hide it behind an "expensive logging enabled" check.
Addresses: #87685.
Release note: None