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

Innodb Purge is very slow on 64-bit Arm architecture



    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4.21, 10.4.22, 10.6.5
    • None
    • Server
    • 64-bit Arm architecture


      • Purge process is very slow on 64-bit Arm architecture.
        == My test machine has 2 cores of CPU and 4 GB of RAM
      • Running the below sysbench command on the mariaDB server, increases the History list length to a very high value and it takes around ~15 minutes for it to drop to a lower value.
        As and when the workload increases, the HLL value reaches a very high value and takes even days to drop to a low value.

      sysbench ./oltp_read_write.lua --db-driver=mysql --mysql-db=test --mysql-user=root --mysql-password=***** --mysql-host= --table_size=16600000 --tables=10 prepare --threads=5

      • Same command run on a MariaDB server set up on "x86_64" machine does "NOT" have any issue.
        == Same number of cpu cores and memory as that used in "ARM64"
        == Same engine configurations (.cnf file)
      • Purge configuration:

      tbd-mar-hll-10421> show global variables like '%purge%';

      Variable_name Value


      aria_log_purge_type immediate
      innodb_max_purge_lag 0
      innodb_max_purge_lag_delay 0
      innodb_max_purge_lag_wait 4294967295
      innodb_purge_batch_size 300
      innodb_purge_rseg_truncate_frequency 128
      innodb_purge_threads 4
      relay_log_purge ON

      8 rows in set (0.00 sec)


        1. arm.read.write.png
          73 kB
          Krunal Bauskar
        2. history length for loading the same amount of the data on arm and x86.png
          28 kB
          Krunal Bauskar
        3. x86.read.write.png
          87 kB
          Krunal Bauskar



            Unassigned Unassigned
            Niranjan Niranjan
            1 Vote for this issue
            5 Start watching this issue



              Git Integration

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