News for hackers. Stuff that matters.
Re:Scala vs. Go TCP Benchmark by jongraehl on Tuesday August 06, 2013 @04:37AM (#6165466)
I'm curious: are you saying Go is M:N and JVM is not? I had to look up M:N - http://en.wikipedia.org/wiki/Thread_(computing)#M:N_.28Hybri... - but ultimately I don't know anything about JVM or Go threading, and your comment didn't go enough into detail for me to follow your reasoning.
Re:Scala vs. Go TCP Benchmark by bsdetector on Tuesday August 06, 2013 @04:42AM (#6165482)
Yes I forget the audience. Go uses M:N scheduling meaning that the OS has M threads and Go multiplexes N of its own threads on top of these. The JVM uses N:1 like basically every other program where the kernel does all scheduling.

The basic problem with M:N scheduling is that the OS and program work against each other because they have imperfect information, causing inefficiencies.

Re:Scala vs. Go TCP Benchmark by gngeal on Tuesday August 06, 2013 @05:42AM (#6165647)
Yes, but can Go actually use anything else? Finely-grained concurrency after the CSP fashion, after all, is the whole driving force behind it, and it's in the language spec.
Re:Scala vs. Go TCP Benchmark by jongraehl on Tuesday August 06, 2013 @03:41PM (#6168714)
Are hybrid approaches worth it (exposing some details so that Go network server can get the right service from the OS)? I'm not sure how much language complexity Go-nuts will take, so they'll probably look for clever heuristic tweaks instead.