You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
When we have multiple providers and OTLP gRPC exporters in our application, gRPC will create a lot of threads for each grpc::Channel, especially in a server machine with a lot CPUs.
Describe the solution you'd like
Exporting OtlpGrpcClient for users and allow construct all OTLP exporters with shared grpc::Channel.
In a system with 132 CPUs, it allocate 250+ threads in just one process with about 4 OTLP gRPC exporters.
We have 600+ processes in ours system and the load average is so high.
Can we add a new gRPC options to allow to build OTLP gRPC exporters from existed gRPC Channel?
I can take this if this feature is accepted.
The text was updated successfully, but these errors were encountered:
marcalff
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Jul 23, 2024
Is your feature request related to a problem?
When we have multiple providers and OTLP gRPC exporters in our application, gRPC will create a lot of threads for each
grpc::Channel
, especially in a server machine with a lot CPUs.Describe the solution you'd like
Exporting
OtlpGrpcClient
for users and allow construct all OTLP exporters with sharedgrpc::Channel
.Additional context
In a system with 132 CPUs, it allocate 250+ threads in just one process with about 4 OTLP gRPC exporters.
We have 600+ processes in ours system and the load average is so high.
Can we add a new gRPC options to allow to build OTLP gRPC exporters from existed gRPC Channel?
I can take this if this feature is accepted.
The text was updated successfully, but these errors were encountered: