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

Query Cache | more metrics

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 26.10
    • 26.10.1
    • cache
    • None
    • MXS-SPRINT-282, MXS-SPRINT-283
    • Hide
      The diagnostics of the cache filter, shown by maxctrl show filter and available in the REST API, now contain statistics on what the cache does: how many statements it has examined, why statements were not cached, the outcome of each lookup and of each attempt to store a result, and the distributions of the lookup, store, server and filter durations and of the size of the cached results. The diagnostics also tell whether the cache storage is connected. The statistics can be cleared with maxctrl clear statistics. The layout of the diagnostics has changed: the information of each thread, earlier reported using the keys thread-0, thread-1, etc., is now in the array threads, and the keys storage and uncached_queries are always present.
      Show
      The diagnostics of the cache filter, shown by maxctrl show filter and available in the REST API, now contain statistics on what the cache does: how many statements it has examined, why statements were not cached, the outcome of each lookup and of each attempt to store a result, and the distributions of the lookup, store, server and filter durations and of the size of the cached results. The diagnostics also tell whether the cache storage is connected. The statistics can be cleared with maxctrl clear statistics. The layout of the diagnostics has changed: the information of each thread, earlier reported using the keys thread-0, thread-1, etc., is now in the array threads, and the keys storage and uncached_queries are always present.

    Description

      he cache filter reports almost nothing about its own behaviour,

      1. why the cache makes queries slower,
      2. why the hit rate is low,
      3. and whether the cache slows MaxScale itself.

      Cloud is asking for 12 metrics from the cache filter.
      All of them are counters, histograms or gauges at decision points that already exist in the filter.

      COUNTERS
        cache.queries                  1  statements the filter examined
        cache.not_cached{reason}       1  dropped before any lookup, by reason
        cache.lookup_results{result}   1  outcome of every lookup
        cache.puts{result}            1  outcome of every store attempt
        cache.uncached_evictions      2  evictions from the known-fast set
       
      HISTOGRAMS (buckets or quantiles, not averages)
        cache.lookup_duration         1  ask the store -> answer in hand
        cache.put_duration            1  store a value; on the client's path
        cache.backend_duration        1  server execution time
        cache.filter_duration         1  routing-thread time inside the filter
        cache.value_bytes             2  result size
       
      GAUGES
        cache.backend_up              1  store reachable
        max_uncached_query_count      2  add to the existing uncached_queries
                                         values (items, hits, misses)
      

      For more details see https://mariadbcorp.atlassian.net/browse/MCDEV-4561

      Attachments

        Issue Links

          Activity

            People

              johan.wikman Johan Wikman
              allen.herrera Allen Herrera
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 5d
                  5d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 1.75d Time Not Required
                  1.75d

                  Git Integration

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