search

avioconsulting / mule-opentelemetry-module

Mule Extension to generate OpenTelemetry traces and metrics
https://avioconsulting.github.io/mule-opentelemetry-module/
BSD 2-Clause "Simplified" License
27 stars 9 forks source link

Tracing Id enabled is causing the performance issues in Mule #209

Open ramakrishnakapa opened 2 months ago

ramakrishnakapa commented 2 months ago

We had an issue when we enabled tracing Id in Mule4, so just wanted to change below current config to new values, need some suggestions in this.

1.can we experiment with increasing this value. A higher max queue size allows more traces to be stored in the queue before they are exported, reducing the frequency of exports and improving performance. If memory consumption is not a concern, try increasing this to 4096 or 8192, then monitor if it reduces the overhead without causing excessive memory usage.

2.Max Batch Export Size (Currently 512). Increasing this value to 1024 could help by reducing the number of batch export operations. However, you should test if this introduces any delay in tracing visibility.

3.Batch Export Delay Interval (Currently 5000 ms).from 5000 ms (5 seconds) to 10000 ms (10 seconds), to reduce the number of exports

  1. Batch Export Timeout (Currently 30000 ms)A slight decrease to 20,000 ms might help if you're seeing delays. However, decreasing this too much could cause frequent timeouts and dropped traces.

Could someone help on the below configuration are ok or will it cause any issues?

ramakrishnakapa commented 2 months ago

![Uploading open.png…]()

manikmagar commented 2 months ago

@ramakrishnakapa As stated in those points, each one has a possible impact of it. I think you should do a performance test with adjustments to find out the impact on your application performance.

In case you haven't seen, you can check some suggestions here - https://github.com/avioconsulting/mule-opentelemetry-module/issues/197#issuecomment-2327976890