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

Improve execute direct (prepare and execute) performance

    XMLWordPrintable

Details

    Description

      Sequence of prepare and then executing require a lot of double work it looks like this:
      Prepare:
      1.1 Parse
      1.2 open and lock tables
      1.3 prepare
      1.4 close tables
      1.5 cleanup
      Execute:
      2.1 open and lock tables
      2.2 prepare
      2.3 optimize
      2.4 execute
      2.5 close tables
      2.6 cleanup

      It is clear, that if we would know that it is direct execute call we can avoid double work on the server side

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. CONPY-16 benchmark current implementation versus Text

          • Major - Major loss of function.
          • Open
          is blocked by

          Task - A task that needs to be done. MDEV-22324 Benchmark parts of query-processing

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. ODBC-286 Very Poor Performance on Remote Connection

          • Major - Major loss of function.
          • Open

          Activity

            People

              sanja Oleksandr Byelkin
              sanja Oleksandr Byelkin
              Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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