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.
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