Divij Vaidya created TINKERPOP-2498:
---------------------------------------
Summary: 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
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)