TelemetryCorrelationHttpModule showing as hot path while analyzing performance

[anjoiype]

While profiling an azure app service using App service .net profile tracer, TelemetryCorrelationHttpModule is showing as hot path frequently. Please find below the stack trace.

We are using Microsoft.ApplicationInsights.TelemetryClient's TrackTrace method to track info to application insights.
What could be the reason for this behaviour?