Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-223

Encapsulate calculations of the table access cost and make them consistent and tunable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • Optimizer
    • None

    Description

      This task is mostly a re-engineering task.
      Currently when calculating the cost of a ref table access method the function best_access_path makes an assumption that any index look-up is performed into a B-tree and the function uses engine independent code for this calculations.
      The cost calculations also use some constants that should be done tunable through system variables tables since these constants may be different for different platform/environments.

      This task is implemented in preparation for the development that will support more realistic cost model for query execution plans.

      [1] http://askmonty.org/worklog/?tid=251

      This is a prerequisite for MDEV-350 and similar to what MySQL 5.7 has under the name "Optimizer Cost Model"

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Igor Babaev (Inactive) made transition -
            Open In Progress
            7d 18h 26m 15
            Igor Babaev (Inactive) made transition -
            In Progress Open
            2d 15h 34m 15
            Sergei Golubchik made transition -
            Open Closed
            4616d 2h 15m 1

            People

              monty Michael Widenius
              igor Igor Babaev (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.