dev-perf

To diagnose API latency and N+1 database issues in .NET Aspire, you analyze distributed trace spans to pinpoint inefficient query patterns and correlate them with specific code paths. This reveals bottlenecks invisible during standard development.

Excessive API latency in distributed .NET systems is often caused by performance anti-patterns like N+1 queries, redundant blob storage reads, and inefficient aggregate rehydration. Distributed tracing identifies these specific bottlenecks in your code paths.

Yes, you need Aspire CLI 13.2 or later to execute trace extraction, span counting, and resource health verification. This environment setup is required to accurately diagnose endpoint latency and identify performance anti-patterns.

You detect redundant blob storage reads and inefficient factory iterations by applying pattern recognition to distributed trace spans. This analysis automatically correlates traces with code paths to pinpoint latency sources.

The best way to verify performance improvements is by following a structured workflow that re-analyzes distributed trace spans after applying optimizations. This confirms the resolution of N+1 queries and validates latency reductions.