apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandesh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXCORE-474) Default unifier placement during M*1 deployment
Date Fri, 08 Jul 2016 15:45:11 GMT

     [ https://issues.apache.org/jira/browse/APEXCORE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandesh updated APEXCORE-474:
-----------------------------
    Description: 
During M*1 deployment, unifier was deployed in the separate container. But there is no advantage
in doing that. 

It is better to make the unifier THREAD_LOCAL with the downstream operator.
( https://issues.apache.org/jira/browse/APEXCORE-482 )


Note:

Recently saw one Kafka ETL app, that had a total of 18 containers allocated, but out of that
5 containers were allocated for default unifiers. It also means lots of time is also spent
in SerDe. 

Implementing this feature will improve the performance greatly.

  was:
During M*1 deployment, unifier was deployed in the separate container. But there is no advantage
in doing that. 

It is better to make the unifier CONTAINER_LOCAL with the downstream operator.


> Default unifier placement during M*1 deployment
> -----------------------------------------------
>
>                 Key: APEXCORE-474
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-474
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Sandesh
>
> During M*1 deployment, unifier was deployed in the separate container. But there is no
advantage in doing that. 
> It is better to make the unifier THREAD_LOCAL with the downstream operator.
> ( https://issues.apache.org/jira/browse/APEXCORE-482 )
> Note:
> Recently saw one Kafka ETL app, that had a total of 18 containers allocated, but out
of that 5 containers were allocated for default unifiers. It also means lots of time is also
spent in SerDe. 
> Implementing this feature will improve the performance greatly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message