V5 logical operator filter performance optimization #212
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.
This vastly improves performance for the and/or filters for tables with many filter fields. (When the filters are defined via a variable, the performance for inlined filters stays roughly the same.)
For example a table with 256 fields, a query with 16 elements for the or-filter, each of the elements doing using 1 operator on 1 field (eg.
{"field0": {"equalTo": "test"}}
)It gets the execution time of
establishOperationPlan
from ~25s down to 10~15ms for the example provided.Time measurements from chrome dev tools' performance tab, and after 10~15 request so JIT could do it's job.
with variables