You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expression evaluation accounts for over a third of incremental query evaluation for certain performance benchmarks
We should introduce a more optimized version of ColumnOp. This more optimal representation should have (1) row positions instead of field names, and (2) a flatter structure.
Every variant of Query that contains references to ColumnOp, we should replace with this new representation. Specifically the IndexJoin and Select variants.
The text was updated successfully, but these errors were encountered:
We can also add a variant LogCmp(OpLogic, OpCmp, ColList, Vec<AlgebraicValue>), which is even more optimal for the common case of a = x && b = y, ... case.
cloutiertyler
changed the title
Optimize expression evaluation
Optimize expression evaluation by changing ColumnOp enum to use row positions instead of field names
May 3, 2024
Centril
changed the title
Optimize expression evaluation by changing ColumnOp enum to use row positions instead of field names
perf(query eval): change ColumnOp to use row positions instead of field names + allocate less in the common case
May 3, 2024
Expression evaluation accounts for over a third of incremental query evaluation for certain performance benchmarks
We should introduce a more optimized version of
ColumnOp
. This more optimal representation should have (1) row positions instead of field names, and (2) a flatter structure.Every variant of
Query
that contains references toColumnOp
, we should replace with this new representation. Specifically theIndexJoin
andSelect
variants.The text was updated successfully, but these errors were encountered: