Hi tison, Just checked https://grpc.github.io/grpc-java/javadoc/io/grpc/inprocess/InProcessChannelBuilder.html , it is an ExperimentalApi. We may make it configurable so that users can choose between NettyChannelBuilder or InProcessChannelBuilder.
Tsz-Wo On Wed, Nov 2, 2022 at 1:00 AM tison <[email protected]> wrote: > Hi, > > I read that we're now always using: > > NettyChannelBuilder channelBuilder = > NettyChannelBuilder.forTarget(target.getAddress()); > > to build the gRPC channel. However, if the ratis client runs in the same > process, is it possible that we try to build an InProcessChannel first so > that gain better performance? > > The motivation is that I'm considering exporting more ports for the ratis > server (process) when writing downstream projects. In this case, when I'm > talking to the ratis cluster (the replicated state machines), I need to use > a ratis client so ratis can handle the consensus part. If I always > initialize a Netty channel for every client, it looks like a significant > performance concern. > > Best, > tison. >
