with optimizedDispatch=true, the queue dispatch thread is redundant (the thread that reads a message does the dispatch) and does not get to service a browse repeatedly. it turns a browse into a one shot operation. The benefits of optimizedDispatch=true are really only apparent with straight through processing when thread context switching is the bottleneck. If you have really large number of destinations, then it may help but you would have to ask your computer to be sure.
On Tue, 25 Jun 2019 at 13:33, cooshal <kushal.gau...@gmail.com> wrote: > > Hi again @gtully, > > I have a query again. > > What if I do not use optimizedDispatch? How does optimizedDispatch help in > scaling. I guess, it does by limiting the message window size. But, > alternately, does it affect the broker's performance? > > Any clarification on this would be very helpful. > > Regards, > Cooshal. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
