[
https://issues.apache.org/jira/browse/ASTERIXDB-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Maxon updated ASTERIXDB-3477:
---------------------------------
Labels: triaged (was: )
> Summarized profile shouldn't compare build and probe times when computing
> min/max time.
> ---------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-3477
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3477
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: RT - Runtime
> Affects Versions: 0.9.9
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
> Labels: triaged
> Fix For: 0.9.10
>
>
> The summary profile in the plan right now doesn't differentiate between the
> build and probe sides of the join when computing the min and max time taken.
> This is misleading because in many cases the build will take far less time,
> and therefore there will be a wide range between min and max time even if all
> probes and builds take roughly the same amount of time respectively. This
> leads to a false appearance of some sort of skew or other performance problem
> when the behavior is normal and expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
