tkalkirill commented on PR #13736:
URL: https://github.com/apache/ignite/pull/13736#issuecomment-6789944638

   > LGTM for the feature check
   > 
   > For future Calcite benchmarks, do I understand correctly that queries 
planned on an upgraded node could run slower during RU? While the feature is 
inactive, Calcite may use the same default estimate of 1,000 rows for tables 
without collected statistics, even if their actual sizes differ greatly
   
   Yes, that’s possible. While the feature is inactive, Calcite uses collected 
statistics when available. Otherwise, it uses the last cached row-count 
estimate or 1,000 if there’s no cached estimate. If tables with very different 
sizes get the same estimate, Calcite can choose a less efficient join order, 
which can make some queries run slower. After RU is finalized, row-count 
estimates resume updating on the normal schedule.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to