Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.2.1
    • 3.2.2
    • General
    • None

    Description

      With big number of tables/schemas, queries to I_S tend to get slower, and can be very slow.

      Attachments

        Issue Links

          Activity

            Lawrin Lawrin Novitsky created issue -
            Lawrin Lawrin Novitsky made changes -
            Field Original Value New Value

            it also makes sense to take a look if I_S queries can be made faster.

            Lawrin Lawrin Novitsky added a comment - it also makes sense to take a look if I_S queries can be made faster.
            Lawrin Lawrin Novitsky made changes -
            Summary An option for catalog functions to use SHOW commands instead of queries to INFORMATION_SCHEMA An option for catalog functions to use combination of simple queries to I_S rather than one complicated
            Lawrin Lawrin Novitsky made changes -
            Summary An option for catalog functions to use combination of simple queries to I_S rather than one complicated An option for catalog functions to use alternative ways of data collecting rather than one complex query to the INFORMATION_SCHEMA
            Lawrin Lawrin Novitsky made changes -

            This ticket will workaround the problem described in the MDEV, i.e. push condition to the JOIN, thus it's, yeah, caused by the MDEV-34015

            Lawrin Lawrin Novitsky added a comment - This ticket will workaround the problem described in the MDEV, i.e. push condition to the JOIN, thus it's, yeah, caused by the MDEV-34015

            Eventually it's just unconditional optimization, i.e. no new option has been introduced. The fix work-around the problem MDEV-34015. It makes performance on my test setup with 400+ schemas on my not very performant laptop acceptable. Testsuites with SQLForeignKeys run 2+-7x times faster.

            Lawrin Lawrin Novitsky added a comment - Eventually it's just unconditional optimization, i.e. no new option has been introduced. The fix work-around the problem MDEV-34015 . It makes performance on my test setup with 400+ schemas on my not very performant laptop acceptable. Testsuites with SQLForeignKeys run 2+-7x times faster.
            Lawrin Lawrin Novitsky made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            Lawrin Lawrin Novitsky made changes -
            Summary An option for catalog functions to use alternative ways of data collecting rather than one complex query to the INFORMATION_SCHEMA SQLForeignKeys performance optimization

            People

              Lawrin Lawrin Novitsky
              Lawrin Lawrin Novitsky
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.