Hi V R,

Two MB should be fine. Many large production services send individual gRPC
messages in the 1 to 20 MB size range. Above that, I would recommend
chunking the data across multiple messages and the use of streaming RPCs.

-Abhishek

On Mon, Jan 31, 2022, 7:42 AM V R <[email protected]> wrote:

> Hello,
> I am working with large images and large meshes in  medical field and I
> need to transfer and serialize those objects directly.
> I read here https://developers.google.com/protocol-buffers/docs/techniques 
> that
> "Protocol Buffers are not designed to handle large messages. As a general
> rule of thumb, if you are dealing in messages larger than a megabyte each,
> it may be time to consider an alternate strategy." Does that mean that I
> can't use gRPC to transfer a mesh with e.g., 2MBytes ?
> Thank you
>
>
> --
> 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/93e19589-45e9-41cd-a8f6-3184d3769fden%40googlegroups.com
> <https://groups.google.com/d/msgid/grpc-io/93e19589-45e9-41cd-a8f6-3184d3769fden%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAMdySNZrt2Heq85bP%2BTODZ6UQGRS6Nzjrg0Ps4CYr7sWwFpPrQ%40mail.gmail.com.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to