Performance: Memoize Encryptor in ActiveRecordEncryptedString::Type #26
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.
Hi, I would like to suggest a small change that has a big impact on performance.
Currently, instantiating the encryptor, especially due to
ActiveSupport::KeyGenerator#generate_key, is a CPU-intensive operation. This can lead to significant overhead if an encryptor is initialized repeatedly for the same attribute type.Rails attribute types, like ActiveRecordEncryptedString::Type, are (if I understand it correctly) typically instantiated once per attribute definition (e.g.,
attribute :secret_field, :encrypted_string). This PR leverages this by memoizing the encryptor instance variable (e.g., using@encryptor ||= ...).With the help of the specs I benchmark that change
This how I found out
Details