You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2015/02/10 22:26:11 UTC
[jira] [Updated] (TEZ-776) Reduce AM mem usage caused by storing
TezEvents
[ https://issues.apache.org/jira/browse/TEZ-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated TEZ-776:
-------------------------------
Assignee: Bikas Saha (was: Siddharth Seth)
Bikas taking this over, since I don't have time to work on this at the moment, and this should go in soon. Allows us to run smaller JVMs for the AM, or handle a lot more tasks on larger JVMs.
> Reduce AM mem usage caused by storing TezEvents
> -----------------------------------------------
>
> Key: TEZ-776
> URL: https://issues.apache.org/jira/browse/TEZ-776
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Bikas Saha
>
> This is open ended at the moment.
> A fair chunk of the AM heap is taken up by TezEvents (specifically DataMovementEvents - 64 bytes per event).
> Depending on the connection pattern - this puts limits on the number of tasks that can be processed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)