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
I am evaluating the performance impact of otel java agent on spring-cloud-gateway application, and I found the performance overhead introduced by agent in this scenario to be very high.
CPU usage doubled in my performance test scenario(I do the performance test with&without otel java agent, and send requests to a spring-cloud-gateway application with 1000 QPS).
The main reason for this performance overhead is because agent use resetOnEachOperator to propagate context on all the operators. But in this scenario, most of the context propagations are useless for users because SCG do not produce any span in those operators. Do we have some ways to avoid those context propagation?
The text was updated successfully, but these errors were encountered:
I am evaluating the performance impact of otel java agent on spring-cloud-gateway application, and I found the performance overhead introduced by agent in this scenario to be very high.
CPU usage doubled in my performance test scenario(I do the performance test with&without otel java agent, and send requests to a spring-cloud-gateway application with 1000 QPS).
I 've analyzed the flame graph
flamegraph.zip
The main reason for this performance overhead is because agent use
resetOnEachOperator
to propagate context on all the operators. But in this scenario, most of the context propagations are useless for users because SCG do not produce any span in those operators. Do we have some ways to avoid those context propagation?The text was updated successfully, but these errors were encountered: