3 ms·
But that's the point I'm trying to show. In Go code all calls are the same. There is no sync/async distinction. In contrast, in C# (or any other similar system
by cyberax 3y ago
But that's the point I'm trying to show. In Go code all calls are the same. There is no sync/async distinction.
In contrast, in C# (or any other similar system) async calls are _expensive_ compared to regular function calls.
- mftb 3y agoYou've misunderstood how go routines work. You need to put the "go" keyword before the function call in order for it to be run concurrently.
- cyberax 3y agoI know perfectly well how goroutines work. 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.
- foton2097 3y agoYou need to add to go keyword to change a normal function to a goroutine. If you would remove async/await and Task/Return from the C# code example, it would perform pretty much the same as Go. 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.
- deleted 3y ago[deleted]