Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Epoll to gRpc #7433

Closed
emeroad opened this issue Nov 19, 2020 · 0 comments · Fixed by #7400 or #7434
Closed

Add Epoll to gRpc #7433

emeroad opened this issue Nov 19, 2020 · 0 comments · Fixed by #7400 or #7434

Comments

@emeroad
Copy link
Member

emeroad commented Nov 19, 2020

Related commit : 66cf5de

https://engineering.linkedin.com/blog/2019/06/espresso-new-netty-framework

The advantages of the native epoll approach include: 1) it implements the edge-triggered model, which performs better than the level-triggered model of Java NIO epoll; and 2) the native epoll generates less garbage on the JVM heap, which reduces the GC pressure for the system.

## AUTO, NIO, EPOLL
profiler.transport.grpc.metadata.${data-type}.channel-type=AUTO

Option : AUTO, NIO, EPOLL
AUTO(default) : If Epoll is available, choose Epoll, if not NIO
NIO : Use NioChannel (NioSocketChannel, NioServerSocketChannel)
EPOLL : Use EpollChannel (EpollSocketChannel, EpollServerSocketChannel)

If a problem occurs, set it to NIO

@emeroad emeroad added this to the 2.2.0 milestone Nov 19, 2020
This was linked to pull requests Nov 19, 2020
emeroad added a commit to emeroad/pinpoint that referenced this issue Nov 19, 2020
emeroad added a commit that referenced this issue Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant