In your Go benchmark code, how is the calculation actually being done across threads? I don't see the `go` keyword anywhere in the source code.
In contrast, in C# (or any other similar system) async calls are _expensive_ compared to regular function calls.
I'm NOT trying to show that Go is faster than async/await or anything similar. I'm showing that nested async/await calls are incredibly expensive compared to regular nested function calls.
If you want to show that async/await calls are expensive, than you should have shown two code samples of C#, one with async/await, and one without.
Or could have done the same for Go, show one example with goroutines, and one without.
But I think everyone already know that async/await and goroutines has it's costs.
The problem is more that you are comparing Go without goroutines (without it's allocation costs) to a C# example with a poor implementation of async/await.
It's trying to show the overhead of the async machinery, compared to "uncolored" unfunctions.