activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: FutureResponse bottleneck when using more than 10 threads
Date Tue, 20 Oct 2015 13:18:57 GMT
I haven't used it, but isn't this exactly what NIO is supposed to fix?  Try
having your clients connect via the nio transport and see if things improve.

Tim
On Oct 19, 2015 10:34 AM, "kal2" <kinfo0114@gmail.com> wrote:

> I tested with 1 connection with 10 threads and that was running fine.
> 1 connection with 15 or more threads seems to be an issue with reading from
> TCP and servicing all the threads??
>
> In our test we tried with 6 connections and we were able to just use 25
> threads.  For our app we needs to service 100's of threads.  For now we are
> use semaphore to limit number of threads calling send api but the latency
> is
> an issue as many threads are trying to wait for few connections (10-25
> depending on # of connections).
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/FutureResponse-bottleneck-when-using-more-than-10-threads-tp4702945p4703119.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message