Start Debugging

Tag: performance

82 posts · Page 4 of 9

2026-07-12 csharp dotnet dotnet-11

How to add output caching to a minimal API in ASP.NET Core 11

A complete, working guide to output caching in an ASP.NET Core 11 minimal API: AddOutputCache and UseOutputCache, CacheOutput on endpoints and MapGroup, named and base policies, Expire, VaryByQuery and VaryByHeader, tag-based eviction with EvictByTagAsync, cache stampede protection, ETag revalidation, and a Redis backing store.

2026-07-11 dotnet-11 csharp async

.NET 11 Runtime Async Drops the EnablePreviewFeatures Flag

As the .NET 11 previews progress toward the November release, Runtime Async has graduated: net11.0 projects opt in with a single MSBuild property, and the runtime libraries themselves now ship compiled on it.

2026-07-11 dotnet performance jit

What is PGO in .NET and do I need to opt in?

PGO (profile-guided optimization) lets the .NET JIT specialize hot code for the types and branches your workload actually hits. Dynamic PGO has been on by default since .NET 8, so on .NET 8 and later you do not need to opt in. Here is what it does, how to see its effect, and the rare cases where you touch the knob.

2026-07-11 dotnet performance jit

What is tiered compilation and how do I reason about it?

Tiered compilation lets the .NET JIT compile every method twice: once fast and unoptimized to get your app running, then again with full optimizations once the runtime knows a method is hot. Here is how tier 0, tier 1, on-stack replacement, and Dynamic PGO fit together, and how to observe and tune them.

2026-07-01 skiasharp dotnet graphics

SkiaSharp 4.0 Ships Stable: 24% Faster GPU Rendering and a Cleaned-Up API

SkiaSharp 4.148.0 is the first stable v4 release. GPU-heavy UIs render up to 24% faster, CPU shaders run ~6x faster, and the legacy API surface is finally retired. Here is what upgrading actually costs you.

2026-06-23 how-to ef-core ef-core-11

How to do keyset (cursor) pagination in EF Core 11

Replace Skip/Take with a WHERE clause that seeks past the last row you saw. Order by a fully unique key, carry the last row's values as a cursor, and EF Core 11 turns the next page into an index seek instead of an OFFSET scan.

2026-06-20 csharp dotnet performance

What is Span<T> in C#, and when does it actually make your code faster?

Span<T> is a stack-only ref struct that points at memory you already own, so it has no backing allocation. It speeds code up in exactly three situations: replacing a heap buffer with stackalloc, slicing without copying, and tight loops where the JIT elides bounds checks. Everywhere else it changes nothing, and across an await it does not compile.

2026-06-20 csharp dotnet async

What is ValueTask<T> and when is it worth it?

ValueTask and ValueTask<T> are structs that let an async method return a result without heap-allocating a Task when it completes synchronously. The win is one fewer allocation on hot paths that usually finish without awaiting. The cost is a strict await-once contract. Here is what the type actually is, how it works, and the narrow set of cases where it earns its keep.

2026-06-19 dotnet native-aot performance

What is Native AOT and what does it cost you?

Native AOT compiles your .NET app to a single self-contained native binary with no JIT, buying fast startup and a small memory footprint. The price is a C toolchain at build time, slower publishes, per-RID builds, no reflection or Reflection.Emit, mandatory trimming, and no Dynamic PGO. Here is the full ledger.

2026-06-15 comparison ef-core ef-core-11

AsNoTracking vs AsNoTrackingWithIdentityResolution in EF Core 11: which should you use?

Use AsNoTracking for read-only queries by default. Reach for AsNoTrackingWithIdentityResolution only when the result graph contains the same entity more than once and your code depends on getting a single shared instance back.