Details

    • MXS-SPRINT-198

    Description

      If THP is enabled, MaxScale should log a warning stating that it might use more memory than is expected.

      For a future release, once static buffers have been allocated, all runtime buffers could disable use of transparent hugepages. The query classifier cache is expected to take up notable amounts of memory and it should not use THP as it is not optimized for it. Some of the buffers in the query canonicalization code could benefit from it but the benefits of it ought to be first measured.

      The effects of THP should also be evaluated to estimate if there is any performance benefit to enabling it in general.

      Attachments

        Activity

          markus makela markus makela added a comment - - edited

          Added a notice level message to 6.4 that is logged whenever transparent hugepage are set to always.

          In newer releases this could be made into a warning if a way to disable it is added.

          markus makela markus makela added a comment - - edited Added a notice level message to 6.4 that is logged whenever transparent hugepage are set to always . In newer releases this could be made into a warning if a way to disable it is added.

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.