rpc_util: Reuse memory buffer for receiving message with stat handlers

### Use case(s) - what problem will this feature solve?

Use shared buffer pool when stats handler(s) is used i.e. address the limitation documented in

https://github.com/grpc/grpc-go/blob/a758b62537636eac84b6f0ce70db850bb55e8268/server.go#L572-L591

### Proposed Solution

?

### Alternatives Considered

?

### Additional Context

See https://github.com/grpc/grpc-go/pull/5862/files#r1171991389.

	// RecvBufferPool returns a ServerOption that configures the server
	// to use the provided shared buffer pool for parsing incoming messages. Depending
	// on the application's workload, this could result in reduced memory allocation.
	//
	// If you are unsure about how to implement a memory pool but want to utilize one,
	// begin with grpc.NewSharedBufferPool.
	//
	// Note: The shared buffer pool feature will not be active if any of the following
	// options are used: StatsHandler, EnableTracing, or binary logging. In such
	// cases, the shared buffer pool will be ignored.
	//
	// # Experimental
	//
	// Notice: This API is EXPERIMENTAL and may be changed or removed in a
	// later release.
	func RecvBufferPool(bufferPool SharedBufferPool) ServerOption {
	return newFuncServerOption(func(o *serverOptions) {
	o.recvBufferPool = bufferPool
	})
	}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

rpc_util: Reuse memory buffer for receiving message with stat handlers #6660

Use case(s) - what problem will this feature solve?

Proposed Solution

Alternatives Considered

Additional Context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development