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 2020/02/20 00:30:00 UTC

[jira] [Commented] (IMPALA-9378) CPU usage for runtime profiles with multithreading

    [ https://issues.apache.org/jira/browse/IMPALA-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040532#comment-17040532 ] 

Tim Armstrong commented on IMPALA-9378:
---------------------------------------

https://gerrit.cloudera.org/#/c/15236/ - IMPALA-9381 should reduce about half of the time spent in CloseImpalaOperation(), according to the flame graph.

> CPU usage for runtime profiles with multithreading
> --------------------------------------------------
>
>                 Key: IMPALA-9378
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9378
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>         Attachments: coord_q5_dop0.svg, coord_q5_dop16.svg
>
>
> [~drorke] reports that significant amounts of time can be spent on the runtime profile with higher values of mt_dop. This can impact query performance from the client's point of view since profile serialisation is on the critical path for closing the query. Also serialising the profile for the webserver holds the ClientRequestState's lock, so can block query progress.
> We should figure out how to make this more efficient.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org