HTTP2 Multiplexing won't work so hot with one very large message. To gain performance you'd want to break the file into pieces. Or you might design your system differently so that the large images / meshes are in blob storage someplace and your gRPC message contains the path to the item.
On Mon, Jan 31, 2022 at 7:44 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 > "Protocol Buffers" 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/protobuf/8478b682-ee3c-4b37-8742-a3ce7160fc00n%40googlegroups.com > <https://groups.google.com/d/msgid/protobuf/8478b682-ee3c-4b37-8742-a3ce7160fc00n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" 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/protobuf/CAA9YwXoO9ic3wpnjpSodcEg2WCTFnhmONtDeov_DZcLoDRNBRA%40mail.gmail.com.
