You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2017/03/14 03:18:41 UTC
[jira] [Created] (DRILL-5352) Extend test framework profile parser
printer for multi-fragment queries
Paul Rogers created DRILL-5352:
----------------------------------
Summary: Extend test framework profile parser printer for multi-fragment queries
Key: DRILL-5352
URL: https://issues.apache.org/jira/browse/DRILL-5352
Project: Apache Drill
Issue Type: Improvement
Affects Versions: 1.10.0
Reporter: Paul Rogers
Assignee: Paul Rogers
Priority: Minor
Fix For: 1.11.0
The recently added test framework has a tool called the {{ProfileParser}} which started as a tool for analyzing run times of single-fragment queries. Over time, it evolved to compare planned and actual cost for multi-fragment queries.
This ticket requests that multi-fagment support be added to the printing of run times.
If a query is single-thread, print the query as in the prior version:
{code}
Op: 0 Screen
Setup: 0 - 0%, 0%
Process: 35 - 0%, 0%
Wait: 16
Memory: 10
Op: 1 Project
Setup: 22 - 1%, 0%
Process: 41 - 0%, 0%
Memory: 5
...
{code}
If the query is multi-fragment and forms a tree, use the format used to display planning vs. actual info:
{code}
03-09 . . Project
Setup: 0 ms - 0%, 0%
Process: 0 ms - 0%, 0%
03-10 . . HashJoin (HASH JOIN)
Setup: 0 ms - 0%, 0%
Process: 5,097,619 ms - 326770%, 73%
03-12 . . . . Project
Setup: 36 ms - 2%, 0%
Process: 180 ms - 11%, 0%
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)