dotnet:perf

Diagnose .NET performance bottlenecks using BenchmarkDotNet and dotnet profiling tools.

2|Updated Apr 19, 2026

Search Tags:#performance #async #performance profiling #GC #EF

Ready to run

npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-perf-dimsour

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet:perf
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet/skills/perf
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-perf-dimsour

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive analysis of .NET application performance, identifying bottlenecks in Entity Framework queries, asynchronous operations, memory allocations, HTTP requests, concurrency issues, and startup configuration.

Core Features & Use Cases

Performance Profiling: Analyze and optimize EF query plans, async bottlenecks, GC pressure, and more.
Efficient Profiling: Utilizes BenchmarkDotNet, dotnet-counters, dotnet-trace, and dotnet-gcdump for detailed performance metrics.
Use Case: Before optimizing slow endpoints or increasing memory usage, use this Skill to pinpoint specific issues like N+1 queries or inefficient async patterns.

Quick Start

Analyze the performance of the endpoint '/api/orders' using the dotnet:perf skill.

Frequently Asked Questions about dotnet:perf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find the cause of high memory usage in a .NET application?▼

To find the cause of high memory usage in a .NET application, you can profile GC pressure and memory leaks using tools like dotnet-gcdump and dotnet-counters to inspect allocation patterns and identify inefficient code paths.

What is the best way to diagnose slow Entity Framework queries in .NET?▼

The best way to diagnose slow Entity Framework queries is to analyze EF query plans to pinpoint specific performance bottlenecks like N+1 queries, utilizing profiling tools to capture detailed metrics before optimizing the endpoints.

How do I troubleshoot async bottlenecks causing latency in .NET?▼

To troubleshoot async bottlenecks causing latency in .NET, profile asynchronous operations using dotnet-trace to inspect inefficient async patterns and concurrency issues, allowing you to resolve the delays causing endpoint latency.

Can I use BenchmarkDotNet to measure .NET startup configuration performance?▼

Yes, you can use BenchmarkDotNet alongside dotnet-counters and dotnet-trace to measure .NET startup configuration performance, capturing detailed metrics to diagnose and optimize startup configurations and concurrency issues.

When should I profile HTTP requests in my .NET application?▼

You should profile HTTP requests in your .NET application when diagnosing performance bottlenecks, specifically before optimizing slow endpoints or addressing latency issues, to inspect concurrency and inefficient code paths.