Cost-based decision between ORDER and SORT plans #8316
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asfernandes
reviewed
Nov 13, 2024
src/jrd/optimizer/Optimizer.h
Outdated
| const double REDUCE_SELECTIVITY_FACTOR_GREATER = 0.05; | ||
| const double REDUCE_SELECTIVITY_FACTOR_STARTING = 0.01; | ||
| const double REDUCE_SELECTIVITY_FACTOR_OTHER = 0.01; | ||
| constexpr double REDUCE_SELECTIVITY_FACTOR_EQUALITY = 0.001; |
Member
There was a problem hiding this comment.
Should not better be inline constexpr?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement cost calculation for the ORDER vs SORT choice when ordering is required for the query. The visible effects are:
ORDER ... INDEXplan is almost never used, being inferior toSORTin most cases -- maybe except some queries withOPTIMIZE FOR FIRST ROWShint, explicit or implicit (e.g.SELECT FIRST). This is already proven in practice to work better.SORTplan may be preferred toORDERfor the defaultOPTIMIZE FOR ALL ROWSscenario if its estimated as being cheaper.ORDERplan will be used always if a suitable index exists. We have a number of QA tests that are affected by this change.The cost calculation will be adjusted once more statistics will be available to the optimizer (e.g. clustering factor).