4 ms·
Concurrency, startup time, memory usage, I/O bound workload.
by rednafi 2y ago
Concurrency, startup time, memory usage, I/O bound workload.
- neonsunset 2y agoAll these .NET has better performance at. Go explicitly trades it off for smaller memory footprint. (Yes, even the things Go is supposed to be good at, because NativeAOT is a more "high-end" solution to the problem - more scalable binary size, and borderline absent startup overhead). Also finely grained concurrency has especially big gap: https://hez2010.github.io/async-runtimes-benchmarks-2024/take2.html https://hez2010.github.io/async-runtimes-benchmarks-2024/tak...
- pier25 2y agoI'm not an expert but from the benchmarks I've seen C# consumes considerably less memory than Goroutines. Eg: https://alexyakunin.medium.com/go-vs-c-part-1-goroutines-vs-async-await-ac909c651c11 https://alexyakunin.medium.com/go-vs-c-part-1-goroutines-vs-...