Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-3193

Per-tablet histogram for scan predicate efficiency

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • metrics, ops-tooling, perf, tablet
    • None

    Description

      Often times slow queries can be the result of a sub-optimal schema for a given workload, e.g. if a scan's predicate is not on a prefix of the primary key. Diagnosing such issues typically takes some understanding of the workloads that are being run against a given table. It'd be nice if there were something more quantitative to understand whether a table(t)'s schema is to blame for a slow scan.

      One thought that comes to mind is maintaining a histogram metric per-tablet of the ratio between the number of rows returned during a given scan and the number of rows iterated through during that scan. A consistently low value of this metric would indicate that predicates applied to the given tablet are doing a lot of IO reading rows that are not in the results set.

      Attachments

        Activity

          People

            Unassigned Unassigned
            awong Andrew Wong
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: