perf(StringRedisTemplate): avoid redundant logger creation in execute(). #3173
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.
Problem Description
Each invocation of
StringRedisTemplate.execute()
creates a newDefaultStringRedisConnection
instance, resulting in repeated initialization of non-static logger instances. This causes redundantLogFactory
lookups that consume an additional 10–15% CPU overhead.Solution
Modify the
private final Log logger
field inDefaultStringRedisConnection
toprivate static final Log logger
.Impact
10–15% reduction in CPU overhead for all Redis client command executions.