activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <bur...@spinn3r.com>
Subject Re: Throughput drop with NIO transport as compared to TCP transport
Date Thu, 09 Apr 2015 01:12:16 GMT
looks like others see a throughput drop:

http://activemq.2283324.n4.nabble.com/NIO-transport-performance-for-ActiveMQ-td4670977.html

On Wed, Apr 8, 2015 at 6:10 PM, Kevin Burton <burton@spinn3r.com> wrote:

> Interesting.  Would be nice to see if there were any benchmarks for this.
>
> On Wed, Apr 8, 2015 at 3:16 AM, samdowning <samdowning2013@gmail.com>
> wrote:
>
>> Hi ActiveMQDevs,
>>
>> I was fiddling around with NIO transport connector in ActiveMQ v5.11.1. I
>> can see the expected thread count reduction when using NIO connector. I
>> did
>> some quick throughput testing also and found that with NIO transport
>> connector the throughput drops by more than 1.5 times to what I get with
>> TCP
>> transport connector.
>>
>> I used 1 subscriber and 1 producer on queue with non-persistent messages
>> to
>> measure the throughput.
>> I tried the same thing 20 producers and 1 subscriber but similar results -
>> throughput with NIO was much less than TCP.
>>
>> Is throughput expected to drop with NIO transport connector?
>>
>> Thanks,
>> Sam
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Throughput-drop-with-NIO-transport-as-compared-to-TCP-transport-tp4694494.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>
> <http://spinn3r.com>
>
>


-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>

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