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

Extremely high cpu usage and slow performance after upgrade from 5.5.52 to 10.1.29

Details

    Description

      After upgrade from MariaDB 5.5.52 to 10.1.19 the performance of our application is about 5 times slower than before.

      It is noticeable that the MariaDB 10.1.19 has a cpu usage of 95%.
      With MariaDB 5.5.52 the cpu usage was only about 5%.

      I appended 2 pictures which shows the difference between these 2 versions.
      For both versions we used the same server with the same test application.
      The only difference is the upgrade of MariaDB.

      The settings of my.ini are appended.

      Attachments

        1. callstacks_10_1_19.txt
          43 kB
        2. MariaDB_5.5.52.png
          MariaDB_5.5.52.png
          78 kB
        3. MariaDB 10.1.19 caches 40000.png
          MariaDB 10.1.19 caches 40000.png
          111 kB
        4. MariaDB 10.1.19 caches 400000.png
          MariaDB 10.1.19 caches 400000.png
          77 kB
        5. my.ini
          1 kB
        6. mysqld.exe_161128_064117.001
          10.00 MB
        7. mysqld.exe_161128_064117.002
          7.03 MB
        8. mysqld.exe_161128_064117.crc
          0.1 kB
        9. mysqld.exe_161202_180716.001
          10.00 MB
        10. mysqld.exe_161202_180716.002
          10.00 MB
        11. mysqld.exe_161202_180716.003
          10.00 MB
        12. mysqld.exe_161202_180716.004
          10.00 MB
        13. mysqld.exe_161202_180716.005
          10.00 MB
        14. mysqld.exe_161202_180716.006
          10.00 MB
        15. mysqld.exe_161202_180716.007
          10.00 MB
        16. mysqld.exe_161202_180716.008
          10.00 MB
        17. mysqld.exe_161202_180716.009
          10.00 MB
        18. mysqld.exe_161202_180716.010
          10.00 MB
        19. mysqld.exe_161202_180716.011
          10.00 MB
        20. mysqld.exe_161202_180716.012
          10.00 MB
        21. mysqld.exe_161202_180716.013
          10.00 MB
        22. mysqld.exe_161202_180716.014
          10.00 MB
        23. mysqld.exe_161202_180716.015
          207 kB
        24. mysqld.exe_161202_180716.crc
          0.1 kB
        25. mysqld.exe.2160.001
          10.00 MB
        26. mysqld.exe.2160.002
          1.42 MB
        27. mysqld.exe.2160.crc
          0.1 kB
        28. Performance of MariaDB 10.1.19.png
          Performance of MariaDB 10.1.19.png
          221 kB
        29. Performance of MariaDB 5.5.52.png
          Performance of MariaDB 5.5.52.png
          258 kB
        30. procdump_output.txt
          4 kB
        31. status.txt
          492 kB
        32. TimeMeasurement for SQLStatements of MariaDB 10.1.19.txt
          21 kB
        33. TimeMeasurement for SQLStatements of MariaDB 5.5.52
          21 kB

        Activity

          Ascending order - Click to sort in descending order
          View 17 older comments
          migra Michael Graf added a comment -

          The Minidump (Plus) created with procdump.exe says INT_DIVIDE_BY_ZERO.

          d:\leutek\mariadb\bin>c:\uti\sysinternals\procdump.exe -mp -e 1 -f "" -x d:\minidumps mysqld.exe --defaults-file=d:\leutek\mariadb\my.ini --console

          I attached the whole output of procdump.exe and the minidump (Plus) mysqld.exe_161202_180716.001 mysqld.exe_161202_180716.002 mysqld.exe_161202_180716.003 mysqld.exe_161202_180716.004 mysqld.exe_161202_180716.005 mysqld.exe_161202_180716.006 mysqld.exe_161202_180716.007 mysqld.exe_161202_180716.008 mysqld.exe_161202_180716.009 mysqld.exe_161202_180716.010 mysqld.exe_161202_180716.011 mysqld.exe_161202_180716.012 mysqld.exe_161202_180716.013 mysqld.exe_161202_180716.014 mysqld.exe_161202_180716.015 mysqld.exe_161202_180716.crc .

          procdump_output.txt

          migra Michael Graf added a comment - The Minidump (Plus) created with procdump.exe says INT_DIVIDE_BY_ZERO. d:\leutek\mariadb\bin>c:\uti\sysinternals\procdump.exe -mp -e 1 -f "" -x d:\minidumps mysqld.exe --defaults-file=d:\leutek\mariadb\my.ini --console I attached the whole output of procdump.exe and the minidump (Plus) mysqld.exe_161202_180716.001 mysqld.exe_161202_180716.002 mysqld.exe_161202_180716.003 mysqld.exe_161202_180716.004 mysqld.exe_161202_180716.005 mysqld.exe_161202_180716.006 mysqld.exe_161202_180716.007 mysqld.exe_161202_180716.008 mysqld.exe_161202_180716.009 mysqld.exe_161202_180716.010 mysqld.exe_161202_180716.011 mysqld.exe_161202_180716.012 mysqld.exe_161202_180716.013 mysqld.exe_161202_180716.014 mysqld.exe_161202_180716.015 mysqld.exe_161202_180716.crc . procdump_output.txt
          wlad Vladislav Vaintroub added a comment -

          Right, this is tracked in another bug filed by you MDEV-11435. Let's keep this one for performance issues only

          wlad Vladislav Vaintroub added a comment - Right, this is tracked in another bug filed by you MDEV-11435 . Let's keep this one for performance issues only
          wlad Vladislav Vaintroub added a comment -

          Also, unless a big deal on your side, it is somewhat easier for us to handle dump files are compressed (zip, 7zip, whatever) rather than split. Minidump for crashes would usually suffice.

          wlad Vladislav Vaintroub added a comment - Also, unless a big deal on your side, it is somewhat easier for us to handle dump files are compressed (zip, 7zip, whatever) rather than split. Minidump for crashes would usually suffice.
          migra Michael Graf added a comment -

          Next time I will zip it

          migra Michael Graf added a comment - Next time I will zip it
          axel Axel Schwenke added a comment -

          The problem was never reproduced. It could have been the same as MDEV-10409.

          axel Axel Schwenke added a comment - The problem was never reproduced. It could have been the same as MDEV-10409 .

          People

            axel Axel Schwenke
            migra Michael Graf
            Votes:
            0 Vote for this issue
            Watchers:
            6 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.