calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Sitnikov <>
Subject Re: JdbcSort not used in plan.
Date Wed, 11 Mar 2015 18:23:30 GMT
More findings:

JdbcJoin.getRows diverges from Join.getRows, so EnumerableJoin has
different cost from JdbcJoin.

org.apache.calcite.rel.core.Project#computeSelfCost uses dRows *
exps.size() in the CPU part of the cost, however VolcanoPlanner just
ignores CPU part of the cost.

We might want start adding "per cell" cost cpu factor, so the cost of
project would be nRows + nRows*nExps*per_cell_cost_factor


View raw message