[Performance] Optimize brewery filters with prefix matching and indices #104
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.
📃 Description
This is an attempt to help with the Slow DB errors in Sentry. Early benchmarking shows promise so I figure it's worth a shot.
🪵 Changelog
➕ Added
name
,city
,state_province
,country
, andpostal_code
(we may not need postal_code, but unless we run into index size issues, it should be fine to keep)perf:gauntlet
to benchmark the changes✏️ Changed
city LIKE 'san%'
since wrapping with%
removes SQLite performance optimizations. SQLite - LIKE optimization. I keptname
the same since it is more practical to not know the full name.📷 Screenshots
With Indices and
LIKE '%pattern%'
With Indices and
LIKE 'pattern%'