[
https://issues.apache.org/jira/browse/TEZ-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331423#comment-15331423
]
Rajesh Balamohan commented on TEZ-3216:
---------------------------------------
MB should be fine. "memory_optimized" and "precise" can be considered for
naming configs. Old stats tend to provide stats information, but more
optimized towards memory and CPU. Latest stats provides a lot better accuracy,
but at the cost of memory/cpu.
It would be good to try running with a DAG with large number of partitions to
check the size of event and the pressure on AM.
> Support for more precise partition stats in VertexManagerEvent
> --------------------------------------------------------------
>
> Key: TEZ-3216
> URL: https://issues.apache.org/jira/browse/TEZ-3216
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Ming Ma
> Assignee: Ming Ma
> Attachments: TEZ-3216-2.patch, TEZ-3216.patch
>
>
> Follow up on TEZ-3206 discussion, at least for some use cases, more accurate
> partition stats will be useful for DataMovementEvent routing. Maybe we can
> provide a config option to allow apps to choose the more accurate partition
> stats over RoaringBitmap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
