Start Debugging

Tag: performance

76 posts · Page 4 of 8

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.

2026-06-14 comparison dotnet aspnetcore

HybridCache vs IMemoryCache vs IDistributedCache in .NET 11: which should you pick?

Default to HybridCache for new caching code in .NET 11. Reach for IMemoryCache only when you need raw single-server speed with no serialization, and IDistributedCache only as a backing store. Here is the decision matrix.

2026-06-12 dotnet-11 csharp linq

LINQ Gets FullJoin and Selector-Free Joins in .NET 11 Preview 5

.NET 11 Preview 5 adds a brand-new FullJoin operator to LINQ plus tuple-returning overloads for Join, LeftJoin, RightJoin, and GroupJoin that drop the result selector entirely.

2026-06-07 aspnetcore dotnet performance

How to use HybridCache in ASP.NET Core 11 with Redis as the L2 cache

Wire HybridCache to a Redis L2 in ASP.NET Core 11: register the service, add the StackExchange Redis distributed cache, and let GetOrCreateAsync give you a two-tier cache with built-in stampede protection and tag invalidation.

2026-06-06 migration csharp dotnet

Migrate from ValueTask<T> back to Task<T>: when and why (.NET 11, C# 14)

A practical checklist for reverting ValueTask and ValueTask<T> return types to Task and Task<T>, what breaks at the call sites, how to verify each change, and how to know whether the swap was ever worth it.

2026-06-04 comparison ef-core ef-core-11

EF Core ExecuteUpdate vs loading entities and SaveChanges: which should you use?

A decision guide and real benchmark for EF Core 11: use ExecuteUpdate for set-based writes by a predicate, and the load-then-SaveChanges path only when you need the change tracker, interceptors, or a complex object graph.

2026-06-03 dotnet performance native-aot

.NET 11 Raises the Minimum CPU Baseline to x86-64-v2

.NET 11 Preview 4 drops support for pre-2013 x86/x64 chips and bumps the JIT baseline to x86-64-v2. Here is what breaks, why, and how to check your hardware before you upgrade.