Thanks for the reply. So after some thinking , i figured if i shorten the size of the worker incoming queue , i can create the scenario where using more than one worker might result in better performance. Any thoughts on how to do that? 

The property topology, receiver.buffer.size should be the the key as mentioned here

But this jira issue says this property is no longer used
Any thoughts on how to change the incoming queue size of the workers? 

On Thursday, 11 February 2016, Matthias J. Sax <> wrote:
I am not sure what you mean:

  - number of worker slots per supervisor
  - topology parameter "number of workers"

Can you clarify?


On 02/11/2016 05:14 AM, anshu shukla wrote:
> Not  like that..  But i have used workers equal to number of cores. Each
> vm with 8 corea.
> On 11 Feb 2016 9:07 am, "Rudraneel chakraborty"
> <
> <>> wrote:
>     more than one worker on same node ? Did u use custom schedule r?
>     because by default, the workers would be spread throughout the cluster

Rudraneel Chakraborty
Carleton University Real Time and Distributed Systems Reserach