drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kkhatua <...@git.apache.org>
Subject [GitHub] drill pull request #756: DRILL-5195: Publish Operator and MajorFragment Stat...
Date Wed, 22 Feb 2017 20:37:06 GMT
GitHub user kkhatua opened a pull request:

    https://github.com/apache/drill/pull/756

    DRILL-5195: Publish Operator and MajorFragment Stats in Profile page

    Improved UI
    1. Introduction of Tooltips
    2. Share of each operator as a percentages of the major fragment and of the query
      - This would help identify the most CPU intensive operators within a fragment and across
the query
    3. Rows emitted by each operator
    4. For a running query, changes to 'last update' and 'last progress' now shows the elapsed
time since.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kkhatua/drill DRILL-5195

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/756.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #756
    
----
commit d044cf53098516ef2936cefaf1cd6907134f461f
Author: Kunal Khatua <kkhatua@maprtech.com>
Date:   2017-02-22T07:06:54Z

    DRILL-5190: Display planning and queued time for a query's profile page
    
    Modified UserSharedBit protobuf for marking planning and wait-in-queue end times. This
will allow for accurately reporting the planning, queued and actual execution times of a query.
    Planning Time:
    In the absence of the planning time's end, for older profiles, the root fragment's (i.e.
SCREEN operator) start time is taken as the estimated end of planning time, and as the estimated
start time of the execution phase. 
    QueueWait Time:
    We do not estimate the queue time if the planning end time is not available. 
    Execution Time:
    We calculate the execution time based on the availability of these 2 planning time. The
computation is done the following way, and reflects a decreasing level of accuracy
    1. Execution time = [end(QueueWait) - endTime(Query)]
    2. Execution time = [end(Planning) - endTime(Query)]
    3. Execution time = [start(rootFragment) - endTime(Query)] - {Estimated}

commit ffd684de09ab9eb586755dcf3a80fccb52ec6940
Author: Kunal Khatua <kkhatua@maprtech.com>
Date:   2017-02-22T19:01:20Z

    DRILL-5195: Publish Operator and MajorFragment Stats in Profile page
    
    Improved UI
    1. Introduction of Tooltips
    2. Share of each operator as a percentages of the major fragment and of the query
      - This would help identify the most CPU intensive operators within a fragment and across
the query
    3. Rows emitted by each operator
    4. For a running query, changes to 'last update' and 'last progress' now shows the elapsed
time since.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message