apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vrozov <...@git.apache.org>
Subject [GitHub] apex-core issue #358: *Review only* [APEXCORE-482]Make the downstream operat...
Date Fri, 22 Jul 2016 20:34:37 GMT
Github user vrozov commented on the issue:

    https://github.com/apache/apex-core/pull/358
  
    Most of the time default unifier (the one that passes tuples unmodified from input streams
to an output stream) is used. For that case, it is necessary to benchmark the change (please
see my previous TODO comment). In general, there should be a way for an application designer
to specify an unifier stream locality for an output port (thread, container, rack or no locality)
with some reasonable defaults (whether it is CONTAINER_LOCAL or THREAD_LOCAL). It should be
also possible to set not only stream locality for the output port, but also buffer server
memory size or queue size. Currently, buffer server queue size when unifier is deployed into
a separate container (Nx1 partition) is the same as the original operator buffer server memory.
This limitation seems to come from using the same StreamMeta both for the unifier output port
and for the partitioned operator output port.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message