Micro optimization for #features on ActiveRecord adapter
#844
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.
I noticed
#featureswas callingGate.all.map(&:key).to_setto get the list of features, which will pull a lot of data over the wire to get the list of features. This replaces it withGate.distinct.pluck(:key).to_set. Thankfully,#featuresis not used in our hot code path internally (get_allwith memoization is used when checking#enabled?), but this could have some impact for those with large actor sets.This benchmark uses an sqlite in-memory database, so the results should be even more dramatic over a network connection.