[
https://issues.apache.org/jira/browse/APEXCORE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543634#comment-15543634
]
ASF GitHub Bot commented on APEXCORE-474:
-----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/apex-core/pull/395
> 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
> Assignee: Sandesh
> Fix For: 3.5.0
>
>
> 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 spent in SerDe.
> Implementing this feature will improve the performance greatly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
