News for hackers. Stuff that matters.

A comment on Evio – Fast event-loop networking for Go. Parent comment

Re:Evio – Fast event-loop networking for Go by pcwalton on Saturday November 04, 2017 @04:23PM (#15626729)
Goroutines are threads. They're just not kernel-level threads.

There have been implementations of pthreads that used an M:N model, for instance.

[ Parent | on HN ]
Re:Evio – Fast event-loop networking for Go by weberc2 on Saturday November 04, 2017 @09:00PM (#15627643)
For my information, why is M:N so successful for Go and not for pthreads? Is M:N more practical for systems with a particular kind of garbage collector?
[ Parent | on HN ]
Re:Evio – Fast event-loop networking for Go by pcwalton on Sunday November 05, 2017 @12:06PM (#15630292)
In my opinion, it's because the Go team put a ton of effort into getting M:N working and didn't rigorously evaluate any other alternatives in Go, once moving GC was implemented.

I'm not convinced that 1:1 wouldn't have been a perfectly reasonable implementation strategy for Go.

[ Parent | on HN ]
Re:Evio – Fast event-loop networking for Go by weberc2 on Sunday November 05, 2017 @02:33PM (#15631117)
This is surprising. It seems like Go gets pretty high praise from all over for its threading model, and it seems like there are relatively few high-performance servers that are built with 1:1. Am I wrong about that? If not, what explains this?
[ Parent | on HN ]