Tag: high-performance-csharp

C#

ValueTask Is Not a Faster Task (Unless You Use It Right)

- - ErcanOPAK comment on ValueTask Is Not a Faster Task (Unless You Use It Right)

Most developers replace Task with ValueTask expecting instant performance gains.The truth: misusing ValueTask can actually make your code slower and more fragile. ValueTask shines only when: The result is often synchronous Allocation pressure matters (high-throughput paths) public ValueTask<int> GetCachedValueAsync() { if (_cache.TryGetValue(“x”, out int value)) return new ValueTask<int>(value); return new ValueTask<int>(LoadFromDbAsync()); } Why it matters:ValueTask […]

Read More
C#

Why Span Can Quietly Make Your C# Code Faster (Without Unsafe Code)

- - ErcanOPAK comment on Why Span Can Quietly Make Your C# Code Faster (Without Unsafe Code)

Most C# performance gains come from avoiding allocations, not from writing complex algorithms.Span<T> lets you work with slices of memory without creating new objects, which means less GC pressure and smoother performance. Why it matters:String slicing, parsing, or buffer manipulation usually creates hidden allocations. Span<T> works directly on memory. ReadOnlySpan<char> span = “Invoice-2026-0198”.AsSpan(); var year […]

Read More