How does Okera scale with varying result sizes (after filtering)?
We expect cost to scale to be sublinearly, i.e. returning twice as many rows should take less than twice as much time.
For example, the performance of a join is not impacted by the number of rows resulted from the join, whether to produce 14k rows or 460 million rows.
Note: Please make sure your benchmark query is not writing to file server.