[
https://issues.apache.org/jira/browse/IMPALA-7694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646122#comment-16646122
]
Balazs Jeszenszky commented on IMPALA-7694:
-------------------------------------------
An easier version of this would be to note time spent waiting for CPU cycles
per fragment instance, since that's the hardest to observe currently.
> Add system resource utilization (CPU, disk, network) timelines to profiles
> --------------------------------------------------------------------------
>
> Key: IMPALA-7694
> URL: https://issues.apache.org/jira/browse/IMPALA-7694
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Lars Volker
> Priority: Major
> Labels: observability, supportability
>
> We often struggle to determine why a query was slow, in particular if it was
> caused by other tasks on the same machine using resources. To help with this
> we should include timelines for system resource utilization to the profiles.
> These should include CPU and disk and network I/O. If it is too expensive to
> include these in all queries we should add a flag to add these to a
> percentage of queries, and a query option to force-enable them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
