This caching is not automatic in grpc or protobuf, but I know that some users use generic (non-proto) message sends to achieve this result: explicitly serialize the message once and then send it out multiple times as a raw message. Hope that helps! - Vijay
On Wednesday, August 14, 2019 at 8:58:47 PM UTC-7, Mark Nuttall-Smith wrote: > > I have a streaming service that sends the same message to multiple > connected clients. > I'm wondering if grpc (or protobuf itself) is smart enough to cache the > serialised form of a message, so that the serialisation cost is not > incurred once per connected client? > Otherwise, what is the cleanest strategy for optimising this? > Thanks, Mark -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/ee2b671c-cb9f-4b8b-96a5-09d806eb1c22%40googlegroups.com.
