[
https://issues.apache.org/jira/browse/TEZ-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955759#comment-14955759
]
Bikas Saha commented on TEZ-1692:
---------------------------------
bq. but it may not be the most efficient removal
??
bq. Do you see something specific that could cause a large increase in resource
utilization
Memory wise I think we should be at parity with the latest patch. Likely also
with cpu. But like I said, this can only be measured.
Not asking for a test case. Just a manual check with some logs (with and
without) should be enough for a sanity check. Earlier we would be under 10ms
tops with various tpcds queries. Just wanted to make sure we aren't regressing
due to some non obvious reason.
> Reduce code duplication between TezMapredSplitsGrouper and
> TezMapreduceSplitsGrouper
> ------------------------------------------------------------------------------------
>
> Key: TEZ-1692
> URL: https://issues.apache.org/jira/browse/TEZ-1692
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-1692.1.txt, TEZ-1692.2.txt, TEZ-1692.3.txt
>
>
> The two are almost identical - with lots of repeated logic. The main
> difference being the mapred / mapreduce InputSplit being grouped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
