Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-177

Collect usage and performance metrics

    Details

    • Type: Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 4.1.0
    • Fix Version/s: 4.1.0
    • Labels:
    • old issue number:
      46

      Description

      I'd like to know how much cpu, physical io, logical io, wait time, blocking time, transmission time was spent for each thread of execution across the hbase cluster, within coprocessors, and within the client's phoenix threadpools for each query.

      Here are some of the problems I want to solve:
      1) every component has one or more configurable threadpools, and I have no idea how to gather data to make any decisions.
      2) queries that I think should be fast turn out to be dog slow, e.g., select foo from bar where foo like 'abc%' group by foo Without attaching a profiler to hbase, which most people won't bother with, it's not clear why it's slow.

        Attachments

        1. phoenix-177-master-v0.patch
          210 kB
          Jesse Yates
        2. phoenix-177-master.patch
          209 kB
          Jesse Yates
        3. phoenix-177-4.0.patch
          209 kB
          Jesse Yates

          Activity

            People

            • Assignee:
              jesse_yates Jesse Yates
              Reporter:
              ryang-sfdc ryang-sfdc
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: