[jira] [Commented] (TINKERPOP-2498) Java client should use Epoll instead of Nio if available

["Stephen Mallette (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302432#comment-17302432 ] 

Stephen Mallette commented on TINKERPOP-2498:
---------------------------------------------

I think that TINKERPOP-2476 which adds a shaded uberjar will prevent use of epoll given package name changes. It is probably worth documenting that when this one is done. 

> Java client should use Epoll instead of Nio if available
> --------------------------------------------------------
>
>                 Key: TINKERPOP-2498
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2498
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.4.9
>            Reporter: Divij Vaidya
>            Priority: Minor
>
> Currently Java client is always configured to use NioEventLoopGroup. However, EpollEventLoopGroup is faster than Nio but is only available on some OS.
> The client should check if Epoll is available and if it is, it should use Epoll instead of Nio.
> Netty's comparison for Nio vs epoll: [https://github.com/netty/netty/wiki/Native-transports]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)