Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-2498

Java client should use Epoll instead of Nio if available

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.4.9
    • Fix Version/s: None
    • Component/s: driver
    • Labels:
      None

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              divijvaidya Divij Vaidya

              Dates

              • Created:
                Updated:

                Issue deployment