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

QC cache thread level memory limit uses the global memory limit

    XMLWordPrintable

Details

    • Bug
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • 25.10.1
    • 25.10.2
    • QueryClassifier
    • None
    • MXS-SPRINT-252

    Description

      During startup MaxScale reports the amount of memory that each thread would use for the query classification results.

      2026-01-22 16:26:32   notice : Query classification results are cached and reused. Maximum memory used per thread: 596.29MiB, in total: 4.65GiB.
      

      The per thread value is what the threads should be using but in reality the threads end up using the total value. This results in excessive memory usage for workloads which do not fit into the cache.

      Attachments

        Activity

          People

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