netty-transport-native-epoll

[patrickjamesbarry]

From my understanding, Glide uses Netty. Lettuce also uses netty and they support netty using native libraries.

Netty provides three platform-specific JNI transports:

• epoll on Linux (netty-transport-native-epoll)
• io_uring on Linux (Incubator). (netty-incubator-transport-native-io_uring)
• kqueue on macOS/BSD (netty-transport-native-kqueue)

Lettuce defaults to native transports if the appropriate library is available within its runtime. Using a native transport adds features specific to a particular platform, generate less garbage and generally improve performance when compared to the NIO based transport. Native transports are required to connect to Redis via Unix Domain Sockets and are suitable for TCP connections as well.

Does Glide support using native libraries such as these? Is this just a netty thing and would be levered if we provided the correct dependency on the corresponding OS?

[xShinnRyuu]

Hi @patrickjamesbarry,

Apologies for the delayed reply. As far as I am aware, there is no way to configure the Netty transport in the current GLIDE release.

Glide has a very specific use case for Netty. It is only used to send data to the Rust middleware, which allows the Rust middleware to communicate with the Valkey server. This is slightly different from how Lettuce directly uses Netty to communicate with the Valkey server.

Important Note: Starting with GLIDE version 2.2.x, we have removed the use of Netty and Unix Domain Sockets in favor of a full JNI-based implementation.

Hopefully this answers your question, feel free to followup if not.