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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no error in this code, but there is an inefficiency in obtaining keys. If a key pair already exists in the cache, it does not need to fetch one from the database each time because
rsa_cache.set(cache_key, rsa_value)
will always overwrite the existing value in the cache even if the key pair hasn't changed.To optimize this function, you can modify it so that only calls to
get_key_pair_by_sql()
actually fetch data from the database:If we know in advance when a full update is likely (for instance, during system startup),
has_new_keys
could be set once at the start of application initialization phase instead of checking every access togenerate
. This avoids unnecessary queries while still providing quick response on demand unless a full refresh might be needed sooner due to some event.