[
https://issues.apache.org/jira/browse/ARTEMIS-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926184#comment-15926184
]
ASF GitHub Bot commented on ARTEMIS-994:
----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/1093
@michaelandrepearce I don't think you really need three parameters for
this... just one would do...
- useEpoll...
the other two you introduced could just use the same parameter, being the
same semantic.. being just epoll.
That way you would configure to use epoll or not with a single switch. If
you need to configure different settings.. than you can just update the
values.. it gets easier on users IMHO.
WDYT?
> 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: 1.5.3, 2.0.0
> 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)
