Performance comparison OTLP over gRPC vs. HTTP #4102
breedx-splk
started this conversation in
General
Replies: 3 comments 1 reply
-
In java even HTTP client brings lots of deps :) I think performance wise they are pretty similar. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Has anybody here any idea about the binary size implications in case of http vs grpc protocols – talking here in perspective of the go SDK |
Beta Was this translation helpful? Give feedback.
0 replies
-
It would also be nice to see the network band with comparison. I would imagine it would make a difference if a commercial collector is used which charges their customer per CPU / network traffic. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Looking at the collector performance page https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/performance.md got me wondering if there's a measurable difference between OTLP/gRPC vs. OTLP/HTTP. Has anybody looked into that?
The java agent is likely switching to a low-dependency OTLP/HTTP exporter as default (gRPC pulls in a lot of deps!)...and I wonder if this matters through a performance lens.
Beta Was this translation helpful? Give feedback.
All reactions