Connecting fast producing operator to a slow consuming operator using CONTAINER_LOCAL port will be a bad application design decision anyway, as it will slowdown producer. In this case it will be better to partition slow downstream operator. Do we currently support partitioning of an operator and deploying all partitions into the same container (CONTAINER_LOCAL)? What stream will be used for multiplexing? InlineStream only supports single not partitioned stream.

Thank you,

Vlad

On 11/18/15 16:01, Chetan Narsude (cnarsude) wrote:
On 11/18/15, 2:43 PM, "Vlad Rozov" <[email protected]> wrote:

Based on the current performance testing I plan to change default value
of PortContext.QUEUE_CAPACITY from 1024 to 1<<19 (still need to do my
homework and see where PortContext.QUEUE_CAPACITY is used).
There are 2 different aspects that need to be considered here. One is
speed of the messaging bus (that you are focusing on) and the second one
is the speed of the operator. What operator cannot process fast enough
sits in the queue and stresses the RAM. That¹s the reason the
queue_capacity default is kept low. I also have a suspicion that this may
cause regression failure and hence is not binary compatible.

‹
Chetan



Thank you,

Vlad

On 11/18/15 11:23, Chetan Narsude (cnarsude) wrote:
What are we doing for size() being inaccurate with spsc?

On 11/18/15, 8:55 AM, "vrozov" <[email protected]> wrote:

Github user vrozov commented on the pull request:

https://github.com/apache/incubator-apex-core/pull/173#issuecomment-1577
77
188
There are 3 applications running on the dev cluster: SpscArrayQueueReservoir around 25 million tuples/s
     CircularBufferReservoir - around 10 million tuples/s
     ArrayBlockingQueueReservoir - around 1.5 million tuples/s



---
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 [email protected] or file a JIRA
ticket
with INFRA.
---

Reply via email to