You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/11/09 00:32:00 UTC
[jira] [Commented] (IMPALA-2343) Capture operator timing
information covering open/close & first/last batch close
[ https://issues.apache.org/jira/browse/IMPALA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680661#comment-16680661 ]
Tim Armstrong commented on IMPALA-2343:
---------------------------------------
Attached some initial work I did in figuring out the best way to do this. The key things are:
* It needs to be low overhead - getting the current time on every GetNext() call may add measurable overhead for some queries.
* It needs to work correctly for subplans.
> Capture operator timing information covering open/close & first/last batch close
> --------------------------------------------------------------------------------
>
> Key: IMPALA-2343
> URL: https://issues.apache.org/jira/browse/IMPALA-2343
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.2.4
> Reporter: Mostafa Mokhtar
> Priority: Minor
> Labels: performance, supportability
> Attachments: 0001-Add-start-and-end-time-to-a-bunch-of-plan-nodes.patch
>
>
> Currently Impala query profile doesn't cover operator level timeline, which makes it difficult to understand the query timeline and fragment dependencies.
> Such information will allow us to provide query swim lanes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org