I'm trying to increase the throughput of one of our trident topologies. Running 
a performance profile on the worker, it's spending a lot of time waiting on a 
ReentrantLock via executor$mk_executor_transfer_fn and DisruptorQueue.publish.

My question is, why is it waiting? It's trying to send tuples to the next bolt 
in the topology, so why does it need to wait before sending the tuple on? What 
is it waiting for? How can I reduce the wait time?

Thanks for the info,
SimonC

Reply via email to