[
https://issues.apache.org/jira/browse/ARTEMIS-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883104#comment-15883104
]
Justin Bertram commented on ARTEMIS-994:
----------------------------------------
{quote}
...use benchmarks to measure the gain.
{quote}
This is essentially what I'm asking about, although you're talking about
retro-active benchmarking. I'm asking about pro-active benchmarking - the kind
of benchmarking that would allow one to identify a performance bottleneck for a
particular use-case. In any case, were going to want to perform benchmarking
to understand what kind of gains this change will make and what use-cases it
will benefit the most. I'm not naive enough to believe it will be the best
option for any and all use-cases. If we can acquire data on this front "for
free" from someone who's already done it (e.g. [~michael.andre.pearce]) then so
much the better. Do you think this is a waste of time, [~clebertsuconic]?
> Support Netty Native Epoll on Linux
> -----------------------------------
>
> Key: ARTEMIS-994
> URL: https://issues.apache.org/jira/browse/ARTEMIS-994
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.0.0, 1.5.3
> Reporter: Michael Andre Pearce (IG)
>
> Netty has support for native epoll, this is available only on linux systems.
> This is more performant.
> http://netty.io/wiki/native-transports.html
> This is inline with supporting asyncio with libaio using such native feature
> to bring perfomance benefits to artemis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
