Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-5136

Increase key_buffer_size

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
      None
    • Story Points:
      0.5
    • Team:
      Data Access and Database

      Description

      I just looked at my qserv-run/etc/my.cnf and I don't see us setting key_buffer_size there. Looking at mysqld run as part of qserv I can see it is set to 128 MB. That is pretty low given we are planning to do lots of joins. Please add an entry in my.cnf that sets it to something higher with a comment that "~20% of available RAM is recommended".

        Attachments

          Issue Links

          is triggered by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-4919 Test performance of vertical-partition joins in mysql

          • Done
          mentioned in

          Page Loading...

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            fritzm Fritz Mueller added a comment -

            Igor Gaponenko, Andy Salnikov: is this a performance parameter we should look at tweaking during KPM50?

            Show
            fritzm Fritz Mueller added a comment - Igor Gaponenko , Andy Salnikov : is this a performance parameter we should look at tweaking during KPM50?
            Hide
            Permalink
            salnikov Andy Salnikov added a comment -

            I guess this is one of the many options that can be tweaked. Do we have profiling metrics in qserv to watch how things evolve when we tweak something?

            Show
            salnikov Andy Salnikov added a comment - I guess this is one of the many options that can be tweaked. Do we have profiling metrics in qserv to watch how things evolve when we tweak something?
            Hide
            Permalink
            gapon Igor Gaponenko added a comment - - edited

            Setting this (as well as many other, similar) parameter statically (in Qserv package) makes very little sense because it may break Qserv in the small RAM deployments (integration tests, etc.). I would rather vote for the deployment time tuneup (for the given number of RAM, cores, etc.) ... which is presently done manually. Perhaps, this step could be automated.

            Show
            gapon Igor Gaponenko added a comment - - edited Setting this (as well as many other, similar) parameter statically (in Qserv package) makes very little sense because it may break Qserv in the small RAM deployments (integration tests, etc.). I would rather vote for the deployment time tuneup (for the given number of RAM, cores, etc.) ... which is presently done manually. Perhaps, this step could be automated.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fritzm Fritz Mueller
              Watchers:
              Andy Salnikov, Fritz Mueller, Igor Gaponenko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.