perf(client): use grpc.SharedBufferPool for grpc.DialOption

When a client library parses incoming gRPC messages, it allocates new buffers
frequently. This can result in the creation of a large number of heap objects.
However, gRPC offers an experimental feature called the shared buffer pool that
can be used to address this issue.

This pull request (PR) aims to optimize the gRPC receiving path using the shared
buffer pool. Various experiments have shown that this optimization leads to a
decrease in CPU time of runtime.gcBgMarkWorkers, depending on the workload.

Refs:
- https://pkg.go.dev/google.golang.org/[email protected]/experimental#WithRecvBufferPool
- https://pkg.go.dev/google.golang.org/[email protected]#SharedBufferPool

pkg/varlog/options.go

@@ -7,6 +7,7 @@ import (
 	"go.uber.org/zap"
 	"google.golang.org/grpc"
 	"google.golang.org/grpc/credentials/insecure"
+	"google.golang.org/grpc/experimental"
 
 	"github.com/kakao/varlog/pkg/types"
 )
@@ -48,6 +49,7 @@ func defaultOptions() options {
 				grpc.MaxCallRecvMsgSize(math.MaxInt32),
 				grpc.MaxCallSendMsgSize(math.MaxInt32),
 			),
+			experimental.WithRecvBufferPool(grpc.NewSharedBufferPool()),
 		},
 	}
 }

vendor/modules.txt

@@ -558,6 +558,7 @@ google.golang.org/grpc/credentials/insecure
 google.golang.org/grpc/encoding
 google.golang.org/grpc/encoding/gzip
 google.golang.org/grpc/encoding/proto
+google.golang.org/grpc/experimental
 google.golang.org/grpc/grpclog
 google.golang.org/grpc/health
 google.golang.org/grpc/health/grpc_health_v1