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

Benchmark AHI to find cases where it's useful

    XMLWordPrintable

Details

    Description

      AHI is probably a subject to removal. It's clear that managing a hash table costs some performance but it's not clear where it could be beneficial.

      One example of harm was found in https://jira.mariadb.org/browse/MDEV-16796 where TRUNCATE was slowed down.

      axel please find cases where AHI improves server speed. Then we can measure whether it's needed at all or not.

      Attachments

        1. AHI_point-select.ods
          44 kB
          Axel Schwenke
        2. AHI_secondary_range.ods
          43 kB
          Axel Schwenke
        3. AHI_vs_writes.ods
          68 kB
          Axel Schwenke

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-12121 Introduce build option WITH_INNODB_AHI to disable innodb_adaptive_hash_index

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20487 Set innodb_adaptive_hash_index=OFF by default

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16796 TRUNCATE TABLE slowdown with innodb_file_per_table=ON

          • Major - Major loss of function.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              axel Axel Schwenke
              kevg Eugene Kosov (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.