I am waiting for the final implementation to check them out. Looks promising.
On Sun, Oct 9, 2016, 12:15 Jan Mercl <0xj...@gmail.com> wrote: > On Sun, Oct 9, 2016 at 11:06 AM Sotirios Mantziaris <smantzia...@gmail.com> > wrote: > > > From what i understand goroutines are not threads either. > > That's the whole point for the original claim. there's not way .net could > ever cope with 100k threads. If you want to compare apples to apples, the > Go version should run only about GOMAXPROCS goroutines. Also, be sure to > make some real work in the goroutine and collect and output its results > (sum for example) to avoid optimizing it away. > > Anyway, then the comparison would become that of picking a random task to > run on a thread vs a full blown goroutine scheduler with the complete > ready/running/wating state handling. > > BTW: How are .net channels doing? ;-) > > -- > > -j > -- Kind Regards, S. Mantziaris -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
