[
https://issues.apache.org/jira/browse/ARTEMIS-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883060#comment-15883060
]
clebert suconic commented on ARTEMIS-994:
-----------------------------------------
[~jbertram] I/O is I/O.. there's nothing you can do to improve performance on
the IO itself.. you have a physical medium somehow, right? Either a DISK, a
SSD, a Network sending waves, whatever you do you can't go faster than physical
barriers..
What you can do is use less CPU and generate less Garbage on the process... I
have seen the implementation when Norman was still at RedHat writing it, and we
have good indications that this will happen.
If we can use less CPU and generate less Garbage that will generate better
throughput on the system, and there is only one way to measure that.. we
implement the thing and use benchmarks to measure the gain. Francesco has a few
written on his github that we can reuse.
> 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)
