-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(all): add CLI flags for gRPC buffer management
This PR introduces new CLI flags to configure buffer management for the gRPC server and client: - `--grpc-server-recv-buffer-pool`: Use the gRPC server's shared buffer pool to parse incoming messages. If not set, the buffer pool will not be used. - `--grpc-server-shared-write-buffer`: Enable sharing the gRPC server's transport write buffer across connections. If not set, each connection will allocate its own write buffer. - `--grpc-client-recv-buffer-pool`: Use the gRPC client's shared buffer pool to parse incoming messages. If not set, the buffer pool will not be used. - `--grpc-client-shared-write-buffer`: Enable sharing the gRPC client's transport write buffer across connections. If not set, each connection will allocate its own write buffer. These flags allow users to fine-tune the memory usage and performance of the gRPC server and client by controlling buffer management. The shared receive buffer pool can reduce memory allocation overhead by reusing the buffer to parse incoming messages across multiple requests or streams. The shared write buffer enables multiple connections to use the same write buffer, reducing memory footprint when handling a large number of connections. By default, these optimizations are disabled to maintain the existing behavior and avoid potential issues in case of improper use. The new flags are added to the following binaries: - varlogsn - varlogmr - varlogadm Notes: - The default values for these flags may need to be adjusted based on performance testing results. - Additional monitoring and metrics for buffer usage could help tune these settings.
- Loading branch information
Showing
6 changed files
with
71 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters