can you explain the performance bottlenecks you're seeing for your use case (heavy thread context switch, lock contention?)?
On Mon, Feb 24, 2014 at 2:17 AM, khandelwalanuj <khandelwal.anu...@gmail.com> wrote: >>> I do not see a reason why you would want idle threads to be kept for a > longer period, especially if there >> are several TaskRunnerFactory > instances in use - this would simply leave idle threads in memory > > I was thinking about load on the broker to create and destroy threads > continuously. Lots of thread creation can affect performance of the broker, > that's why I am thinking to retain the threads in memory. > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/What-is-the-effect-of-dedicatedTaskRunner-Attribute-tp2363191p4678299.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
