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 "Bikramjeet Vig (Jira)" <ji...@apache.org> on 2020/04/15 18:14:00 UTC

[jira] [Resolved] (IMPALA-9422) Improve join builder profiles

     [ https://issues.apache.org/jira/browse/IMPALA-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bikramjeet Vig resolved IMPALA-9422.
------------------------------------
    Fix Version/s: Impala 4.0
       Resolution: Fixed

> Improve join builder profiles
> -----------------------------
>
>                 Key: IMPALA-9422
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9422
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Bikramjeet Vig
>            Priority: Major
>              Labels: multithreading
>             Fix For: Impala 4.0
>
>
> We should clean up/improve the join builder profiles for the separate build.
> First, for the separate build, we should ensure that all time spent in the builder is counted against the builder. E.g. calls into public methods like BeginSpilledProbe(). These should be counted as idle time for the actual join implementation, so that we can see that the time is spent in the (serial) builder instead of the (parallel) probe.
> We might need to fix things like Send() being called by RepartitionBuildInput, resulting in double counting.
> Second, we should revisit the assortment of timers - BuildRowsPartitionTime, HashTablesBuildTime, RepartitionTime. Maybe it makes sense to make them child counters of total time to make the relationship clearer.



--
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