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

provide various information about vector indexes

Details

    Description

      Either status variables or new INFORMATION_SCHEMA tables or additional columns in the existing INFORMATION_SCHEMA tables and SHOW commands to show some of

      • size of the vector index
      • number of deleted rows (can be estimated by number of rows in the hlindex table minus number of rows in the main table)
      • actual cache size
      • number of layers
      • whether randomization is used
      • search stats like (for example)
        • number of distance invocations
        • number of distance_greater_than shortcuts
        • number of jumps per layer

      but only values that can actually be used for something

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-32887 vector search

          • Critical - Crashes, loss of data, severe memory leak.
          • Stalled

          New Feature - A new feature of the product, which has yet to be developed. MDEV-35821 vector index sizes are not in information_schema.TABLES nor SHOW TABLE STATUS

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            serg Sergei Golubchik created issue -
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            serg Sergei Golubchik made changes -
            Description Either status variables or new INFORMATION_SCHEMA tables or additional columns in the existing INFORMATION_SCHEMA tables and SHOW commands to show some of
            * size of the vector index
            * number of deleted rows (can be estimated by number of rows in the hlindex table minus number of rows in the main table)
            * actual cache size
            * number of layers
            * search stats like (for example)
            ** number of distance invocations
            ** number of distance_greater_than shortcuts
            ** number of jumps per layer

            but only values that can actually be used for something             		Either status variables or new INFORMATION_SCHEMA tables or additional columns in the existing INFORMATION_SCHEMA tables and SHOW commands to show some of
            * size of the vector index
            * number of deleted rows (can be estimated by number of rows in the hlindex table minus number of rows in the main table)
            * actual cache size
            * number of layers
            * whether randomization is used
            * search stats like (for example)
            ** number of distance invocations
            ** number of distance_greater_than shortcuts
            ** number of jumps per layer

            but only values that can actually be used for something
            serg Sergei Golubchik made changes -
            Issue Type Task [ 3 ] New Feature [ 2 ]
            serg Sergei Golubchik made changes -
            Component/s Vector search [ 20205 ]
            serg Sergei Golubchik made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            serg Sergei Golubchik made changes -
            Component/s Performance Schema [ 15627 ]
            serg Sergei Golubchik made changes -

            People

              Unassigned Unassigned
              serg Sergei Golubchik
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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