Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
Impala 2.8.0
Description
In profiles there is no way for users to know that TotalWallClockTime refers to the total across all fragment threads. We should prefix the counters with a name that makes this clear.
Averaged Fragment F00:(Total: 56s192ms, non-child: 0.000ns, % non-child: 0.00%) split sizes: min: 18.14 GB, max: 18.31 GB, avg: 18.22 GB, stddev: 49.03 MB completion times: min:1m58s max:2m20s mean: 2m10s stddev:8s108ms execution rates: min:133.10 MB/sec max:157.85 MB/sec mean:143.78 MB/sec stddev:8.78 MB/sec num instances: 7 - AverageThreadTokens: 6.55 - BloomFilterBytes: 1.00 MB (1048576) - InvoluntaryContextSwitches: 25.35K (25352) - PeakMemoryUsage: 15.75 GB (16908711123) - PerHostPeakMemUsage: 35.00 GB (37578534499) - RowsProduced: 69.25M (69246528) - TotalNetworkReceiveTime: 6s389ms - TotalNetworkSendTime: 4s881ms - TotalStorageWaitTime: 1s267ms - TotalWallClockTime: 14m17s - SysTime: 36s266ms - UserTime: 2m16s - VoluntaryContextSwitches: 1.00M (1000378) Fragment Instance Lifecycle Timings: - ExecTime: 1m14s - ExecTreeExecTime: 45s547ms - OpenTime: 56s148ms - ExecTreeOpenTime: 55s686ms - PrepareTime: 44.668ms - ExecTreePrepareTime: 2.667ms