Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4855

While writing query GUI response very slow

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 23.08.3
    • 23.08.4
    • maxgui
    • None
    • MXS-SPRINT-195

    Description

      In Maxscale 23.08.3 version, the GUI responds rather slowly when writing a select query after choosing the schema and expanding the tables. Typing should display instantaneously, but the GUI query editor takes a few seconds to load the letters once we type each letter.

      However, the Maxscale 23.02.2 version is quick and does not have any latency when we input a letter, it appears quickly.

      NOTE: I have tested on the Google and Mozilla browsers but observed same issue on both browsers.

      Attachments

        1. gui.zip
          3.70 MB
        2. image-2023-11-09-16-38-35-622.png
          image-2023-11-09-16-38-35-622.png
          41 kB
        3. screenshot-1.png
          screenshot-1.png
          27 kB
        4. screenshot-2.png
          screenshot-2.png
          31 kB

        Issue Links

          Activity

            Thanks Duong,

            naresh.chandra@copart.com Naresh Chandra added a comment - Thanks Duong,
            thien.ly Thien Ly added a comment - - edited

            Hi naresh.chandra@copart.com,
            We've addressed the typing slowness issue in the upcoming 23.08.04 release.

            Regarding the slowness issue with changing the query tab, it requires a more intricate solution. The root cause comes from the large number of tables present (715 in your case - DOM pollution issue). In brief, we need to implement a virtualized tree for the schema explorer which requires changing the core component so we can't easily add it to the upcoming release. I added a separate ticket for that issue.
            As a workaround, you could collapse the "Tables" node after expanding it to avoid this slowness while changing the query tab.

            thien.ly Thien Ly added a comment - - edited Hi naresh.chandra@copart.com , We've addressed the typing slowness issue in the upcoming 23.08.04 release. Regarding the slowness issue with changing the query tab, it requires a more intricate solution. The root cause comes from the large number of tables present (715 in your case - DOM pollution issue). In brief, we need to implement a virtualized tree for the schema explorer which requires changing the core component so we can't easily add it to the upcoming release. I added a separate ticket for that issue. As a workaround, you could collapse the "Tables" node after expanding it to avoid this slowness while changing the query tab.

            Hi Duong,

            Thanks for the update. When will be the next version release date??

            naresh.chandra@copart.com Naresh Chandra added a comment - Hi Duong, Thanks for the update. When will be the next version release date??
            thien.ly Thien Ly added a comment -

            Hi naresh.chandra@copart.com, we released 23.08.03 about 3 weeks ago, so I don't think we're gonna release 23.08.04 any time soon. But you can expect it to be released before February 2024.

            thien.ly Thien Ly added a comment - Hi naresh.chandra@copart.com , we released 23.08.03 about 3 weeks ago, so I don't think we're gonna release 23.08.04 any time soon. But you can expect it to be released before February 2024.

            Hi Duong,

            Thanks for the update.

            naresh.chandra@copart.com Naresh Chandra added a comment - Hi Duong, Thanks for the update.

            People

              thien.ly Thien Ly
              naresh.chandra@copart.com Naresh Chandra
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.