-
Notifications
You must be signed in to change notification settings - Fork 646
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
Document recommendation about using netty-tcnative for optimizing TLS performance #344
Comments
I've done as you say,but id dosen't seem to work.only add a denpendency?needn't more operation? |
It's my fault,I change the version of netty-tcnative-boringssl-static.It works,thank you. |
Hi, when we say netty-tcnative boosts TLS/https performance by multiple factors, is it include netty-tcnative-boringssl-static ? |
yes |
In the documentation it is specified that |
@lhotari Is there a way of specifying all platforms in Gradle? Our JARs are being built from Jenkins but then run from Docker which is a different OS. |
Using netty-tcnative boosts TLS/https performance by multiple factors.
Netty wiki explains some benefits of netty-tcnative:
It should be documented as a recommendation to use netty-tcnative when using TLS/https . In modern applications, most connections use TLS.
netty-tcnative-boringssl-static is a statically compiled dependency that can be used without any prerequisites and contains native libraries for Mac OSX, Linux and Windows.
For Gradle, add:
or for Maven add:
The disadvantage of the multi-platform dependency is the large size of it. It's also possible to use platform specific classifiers of the netty-tcnative-boringssl-static artifact. For example, for just supporting Linux:
For Gradle, add:
or for Maven add:
On Linux, the
netty-tcnative-boringssl-static
library in Maven Central doesn't support Alpine Linux / libmusl. It's compiled for glibc based Linux distributions.The text was updated successfully, but these errors were encountered: