I am not sure what do you mean by "if we do not manually send a protobuf msg to grpc and only call APIs generated by gRPC", but max frame size is applied to all HTTP2 frames regardless (like you said, it belongs to the transport layer), so there shouldn't been any distinction between what users put or use. grpc will take whatever the user want to send, and create frame(s) for the data. If the data is larger than a single frame (4MB) can contain, then multiple frames will be created to transmit the data.
And in most cases, there is no need to change the default max frame size. But if you want to optimize your application's performance, you may want to experiment with different values max frame size depending on the message size you are transmitting. On Wednesday, August 8, 2018 at 9:40:30 PM UTC-7, Grpc learner wrote: > > The default max frame size is 4Mb, how can I determine a good number for > max frame size? > Addition, the `max frame` belongs to the transportation layer, if we do > not manually send a protobuf msg to grpc and only call APIs generated by > gRPC, the grpc always send a msg under 4Mb(the default value) ? > Correct me if I am wrong. > > > > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5eca7fc4-8c36-4e6a-ae10-8ca6e0965598%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
