Creating millions of coroutines or "goroutines" isn't really interesting by itself. I believe the real questions for me are:
1. is Go scheduler better than Linux scheduler if you have a thousand concurrent goroutines or threads?
2. is really creating goroutines that much faster than creating a native thread?
3. are gorutines relevant for long lived and computationally intensive tasks or just for short lived I/O task?
4. What is the performance of using channels between goroutines compared to native threads?
tbh, I have read several of respected articles that criticize Golang goroutines in terms of performance and I am not really sure that Golang's only virtue imho which is simple concurrency is performant at all
1. is Go scheduler better than Linux scheduler if you have a thousand concurrent goroutines or threads?
2. is really creating goroutines that much faster than creating a native thread?
3. are gorutines relevant for long lived and computationally intensive tasks or just for short lived I/O task?
4. What is the performance of using channels between goroutines compared to native threads?
tbh, I have read several of respected articles that criticize Golang goroutines in terms of performance and I am not really sure that Golang's only virtue imho which is simple concurrency is performant at all