.NET Profiling

Trigger On

• the repo needs performance or runtime profiling for a .NET application
• the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock contention, or startup diagnostics
• the team wants official CLI-based diagnostics without depending on dnx

Value

• produce a concrete project delta: code, docs, config, tests, CI, or review artifact
• reduce ambiguity through explicit planning, verification, and final validation skills
• leave reusable project context so future tasks are faster and safer

Do Not Use For

• replacing realistic performance tests or load tests with ad-hoc tracing alone
• production heap collection when the pause risk has not been accepted
• GUI-only workflows that the repo cannot automate or document