4 ms·
> Go turned out to be a pretty bad choice for container tech due to its awful multithreaded runtime. What you mean by that? What makes it a bad choice in conte
by lossolo 7y ago
> Go turned out to be a pretty bad choice for container tech due to its awful multithreaded runtime.
What you mean by that? What makes it a bad choice in context of containers ? I ask because I know how Go is using M:N threading model in its runtime and what linux containers really are, but I can't find a reason in which I would use word awful to describe using Go in this context.
- cpuguy83 7y agoBecause container tech is often per-thread which you have no control over in Go. There is runtime.LockOSThread(), but then if something happens to spin up a new groutine from there it will be done on a new os thread and not running in the container context. It's not totally impossible to work around, however it does make many things incredibly frustrating.