Can anyone point me to some example of a .net project that doesn't scale because not using async await for IO?

I'm not sure how to measure impact of not doing this...

What kind of scaling are you referring to here? No matter how many times I read the post I still feel a need for clarity

@Unradelic web services our clients integrate with via http. So simple API but under high load.

@craig939393 you can always scale horizontally and that’s fine for either async code or not. If you use async and use async libs for your IO then you’ll be able to get more throughput on your existing machines before you need to horizontally scale. YMMW depending on how much IO you do.