> It helps keep the app responsive while using less resources and avoiding lockups and crashes.
it actually uses more resources. async has a cost, but it is really low.
Re:.NET 5.0
by asyncawaaait on Tuesday November 10, 2020 @04:39PM
(#25052338)
There is a resource tradeoff. async/await has a minor CPU/memory impact, but it can also free up threads to do other work during an I/O bound operation.
Threads have their own resource cost.
.NET is used by millions of developers. Strong and scalable foundations matter, and performance is an explicit goal with asp.net being one of the fastest web frameworks. Async is a core part of this.
There's very little - if any - overhead that you need to worry about with async code from the language to Visual Studio.