dotnet-profiling

To identify CPU hotspots and memory growth in a .NET application, use dotnet-trace for CPU and memory profiling, and dotnet-gcdump for managed heap snapshots. These official CLI tools produce repeatable diagnostics artifacts to locate runtime anomalies and performance bottlenecks.

Profiling .NET startup delays and contention in production is best done using dotnet-trace, which captures startup and contention data. This official CLI workflow standardizes diagnostics across development and production scenarios without requiring heavy tooling.

Use dotnet-counters to monitor live health signals by collecting real-time baseline metrics from your .NET application. This official CLI tool provides immediate runtime health visibility, enabling you to triage slow APIs and detect anomalies before capturing deeper diagnostics.

Yes, you can capture a managed heap snapshot to triage a slow .NET API using dotnet-gcdump. This official CLI tool generates heap analyses that pinpoint memory growth sources, completing a diagnostic workflow that starts with live metrics and CPU traces.

No, this .NET diagnostics workflow does not require external profiling dependencies. It standardizes exclusively on official CLI tools—dotnet-counters, dotnet-trace, and dotnet-gcdump—to deliver repeatable diagnostics artifacts and actionable remediation guidance.

You should avoid using dotnet-trace for .NET performance profiling when you only need a quick overview of runtime health, as it captures deep CPU and memory traces. For baseline metrics without the overhead, start with dotnet-counters instead.