I had just assumed it was being compressed by HTTP2, but I guess that is not the case. Thanks for the correction.
On Monday, March 19, 2018 at 1:18:34 PM UTC-7, [email protected] wrote: > > Hi Aaron, > Compression in gRPC is optional and not enabled by default. Did you see > something that led you believe your traffic was compressed? > > > On Thursday, March 15, 2018 at 3:36:52 PM UTC-7, Aaron Beitch wrote: >> >> Hello, >> >> We just had a minor panic internally at my company when we realized that >> gzip compression is not enabled on any of our gRPC services. After making >> the code changes to enable gzip we then had the realization that the http2 >> client/server is probably already doing compression. >> >> A couple questions: >> >> 1) Do gRPC messages get compressed by the http2 layer by default? >> >> 2) Why would I enable gzip compression in gRPC if it is being done by >> http2? Is the answer that I shouldn't be enabling gzip compression in gRPC, >> but the flexibility is there in case I want to enable a different >> compression scheme or I'm not using http2? >> >> I'm using the gRPC-Go, btw, if that makes any difference. >> >> Thanks, >> Aaron >> > -- 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/a261cb73-3f7b-4150-a489-2854c30e9692%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
