You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue.
What version of gRPC are you using?
grpc-go 1.11
What version of Go are you using (go version)?
go version go1.8.4 linux/amd64
What operating system (Linux, Windows, …) and version?
Linux
What did you do?
I've read golang's TLS and gRPC's http2 server code.
What did you expect to see?
gRPC provides means to disable read buffer for better performance while decreasing memory usage.
What did you see instead?
It looks like both TLS and gRPC have their own read buffers (by default ~8-16KB and 32KB accordingly) and gRPC buffer just performs memory copies from TLS buffer on every Read call without affecting number of syscalls while paying extra memory and cpu costs (for having buffer and performing extra memory copies accordingly).
Is it possible to provide grpc.DisableReadBuffer or similar option, please?
The text was updated successfully, but these errors were encountered:
Please answer these questions before submitting your issue.
What version of gRPC are you using?
grpc-go 1.11
What version of Go are you using (
go version
)?go version go1.8.4 linux/amd64
What operating system (Linux, Windows, …) and version?
Linux
What did you do?
I've read golang's TLS and gRPC's http2 server code.
What did you expect to see?
gRPC provides means to disable read buffer for better performance while decreasing memory usage.
What did you see instead?
It looks like both TLS and gRPC have their own read buffers (by default ~8-16KB and 32KB accordingly) and gRPC buffer just performs memory copies from TLS buffer on every Read call without affecting number of syscalls while paying extra memory and cpu costs (for having buffer and performing extra memory copies accordingly).
Is it possible to provide
grpc.DisableReadBuffer
or similar option, please?The text was updated successfully, but these errors were encountered: