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

Add InnoDB engine information to the slow query log

Details

    Description

      Percona server has some useful InnoDB status information in the slow query log.
      The Percona Performance Monitor can provide useful graphs from these

      This task is to add some of the most useful ones, but with less code.
      The code should also be engine independent, so that it is easy to add
      monitoring of other engines!

      The current task will add the following new information to the slow query log if enabled with
      --log-slow-verbosity=innodb

       # Pages_accessed: 184  Pages_read: 95  Pages_updated: 0  Undo_rows_read: 1
       # Pages_read_time: 17.0204  Engine_time: 248.1297
      

      Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
      Page_* variables are for now only for InnoDB.

      Attachments

        Issue Links

          Activity

            monty Michael Widenius created issue -
            monty Michael Widenius made changes -
            Field Original Value New Value
            Description Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb

            # Pages_accessed: 17 Pages_reads: 10 Pages_updated 0
            # Pages_io_time 1.2767 Engine_time: 34.0872

            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
            # Pages_accessed: 17 Pages_reads: 10 Pages_updated 0
            # Pages_io_time 1.2767 Engine_time: 34.0872
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            monty Michael Widenius made changes -
            Description Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
            # Pages_accessed: 17 Pages_reads: 10 Pages_updated 0
            # Pages_io_time 1.2767 Engine_time: 34.0872
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
            # Pages_accessed: 17 Pages_reads: 10 Pages_updated: 0
            # Pages_read_time 1.2767 Engine_time: 34.0872
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            monty Michael Widenius made changes -
            Description Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
            # Pages_accessed: 17 Pages_reads: 10 Pages_updated: 0
            # Pages_read_time 1.2767 Engine_time: 34.0872
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
                # Pages_accessed: 184 Pages_read: 95 Pages_updated: 0 Undo_rows_read: 1
                 # Pages_read_time: 17.0204 Engine_time: 248.1297
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            monty Michael Widenius made changes -
            Description Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
                # Pages_accessed: 184 Pages_read: 95 Pages_updated: 0 Undo_rows_read: 1
                 # Pages_read_time: 17.0204 Engine_time: 248.1297
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            Percona server has some useful InnoDB status information in the slow query log.
            The Percona Performance Monitor can provide useful graphs from these

            This task is to add some of the most useful ones, but with less code.
            The code should also be engine independent, so that it is easy to add
            monitoring of other engines!

            The current task will add the following new information to the slow query log if enabled with
            --log-slow-verbosity=innodb


            {code:java}
             # Pages_accessed: 184 Pages_read: 95 Pages_updated: 0 Undo_rows_read: 1
             # Pages_read_time: 17.0204 Engine_time: 248.1297
            {code}


            Engine_time is how many milliseconds is spent inside engine calls (similar as with analyze).
            Page_* variables are for now only for InnoDB.


            julien.fritsch Julien Fritsch made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            psergei Sergei Petrunia made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.11 [ 27614 ]
            Fix Version/s 11.0 [ 28320 ]
            Fix Version/s 10.11.5 [ 29019 ]
            monty Michael Widenius made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            monty Michael Widenius made changes -
            Fix Version/s 10.6.15 [ 29013 ]
            Fix Version/s 10.11 [ 27614 ]
            Fix Version/s 11.0 [ 28320 ]
            monty Michael Widenius made changes -
            issue.field.resolutiondate 2023-07-07 11:45:38.0 2023-07-07 11:45:38.761
            monty Michael Widenius made changes -
            Fix Version/s 10.9.8 [ 29015 ]
            Fix Version/s 10.10.6 [ 29017 ]
            Fix Version/s 10.11.5 [ 29019 ]
            Fix Version/s 10.8.8 [ 28518 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            Fix Version/s 10.8.8 [ 28518 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            ralf.gebhardt Ralf Gebhardt made changes -
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            psergei Sergei Petrunia made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -

            People

              monty Michael Widenius
              monty Michael Widenius
              Votes:
              0 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.