Resource management for Google gRPC library · envoyproxy/envoy#11024

(1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import

area/grpcarea/securityhelp wantedpriority/high

Repository metrics

We need to make some improvements to the treatment of resource management in the use of Google gRPC. Specifically:

On the send-side, in google_async_client_impl.h, we need the equivalent of #10882, but working with the queued write buffers (which are in a dequeue, not a watermarked buffer).
On the receive side, we need to configure buffer limits, see https://github.com/grpc/grpc/blob/a9a0739dc8acfeb46105ebc1ed1f81a1734bd801/include/grpcpp/resource_quota_impl.h and https://github.com/grpc/grpc/blob/311bf04ec94d7def98d80da050fd55feaabb1398/include/grpcpp/support/channel_arguments_impl.h#L90. Default resource quota is unbounded.

Research direction: Examine PR #10882 for the send side watermarked buffer pattern, then implement a similar approach for the dequeue in google async client impl.h. For the receive side, review the gRPC resource quota header files to configure buffer limits in the channel arguments.
Tech stack: grpc
Domain: backendinfrastructure
Issue type: Refactor
Difficulty: 4
Estimated time: Half day
Activity status: Fresh
Clarity: Mostly clear
Prerequisites: C++gRPCEnvoy internals
Newbie friendliness: 20