Matthew Jacobs created IMPALA-5870:
--------------------------------------
Summary: Partial sort profile counters don't make sense for
partial sort
Key: IMPALA-5870
URL: https://issues.apache.org/jira/browse/IMPALA-5870
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 2.10.0
Reporter: Matthew Jacobs
Assignee: Thomas Tauber-Marshall
The profile counters for the partial sort don't all make sense:
{code}
SORT_NODE (id=2):(Total: 13s492ms, non-child: 2s098ms, % non-child:
15.55%)
- InMemorySortTime: 880.839ms
- InitialRunsCreated: 1 (1)
- PeakMemoryUsage: 93.48 MB (98016393)
- RowsReturned: 804.95K (804951)
- RowsReturnedRate: 59.53 K/sec
- SortDataSize: 89.40 MB (93742171)
- SpilledRuns: 0 (0)
- TotalMergesPerformed: 0 (0)
{code}
We should probably indicate this is a partial sort, and consider:
* rename/remove InitialRunsCreated/SpilledRuns - we care here about the number
of partial sorts, not sure how to phrase that
* check if this makes sense: SortDataSize
* remove TotalMergesPerformed
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
