I think it is the same even in local shuffling. It will go to the worker receive buffer from which it gets transferred to the executor disruptor queue. So yes the executor would be able to go as fast that thread is able to tuples, provided the Bolt takes less time than copy of the messages from the worker receive buffer to the disruptor queue (which more often than not is not the case). You can increase the disruptor queue size to see if that improves any performance in your scenario.
On Mon, Aug 17, 2015 at 6:21 AM Vincenzo Gulisano < [email protected]> wrote: > Hi, > something that is not clear to me (and I cannot find clear answers to > this), is whether the send thread of an executor A is able to directly move > a tuple to the input queue of another executor B (within the same worker of > course) or whether all output tuples have to go through the shared transfer > queue and then copied to input queues by the worker send thread. > In such a case, wouldn't such a thread be a bottleneck? A worker would be > able to go as fast as this thread is able to move tuples around, isn't it? > > Thanks! >
