Not only that, but in the context-switching overhead, the numbers provided are not appropriate to golang - because go's function calling convention assumes fewe

Not only that, but in the context-switching overhead, the numbers provided are not appropriate to golang - because go's function calling convention assumes fewer registers are saved, thus reducing context switching overhead. From : https://codeburst.io/why-goroutines-are-not-lightweight-threads-7c460c1f155f https://codeburst.io/why-goroutines-are-not-lightweight-thre... "In Go, this means only 3 registers i.e. PC, SP and DX (Data Registers) being updated during context switch rather than all registers (e.g. AVX, Floating Point, MMX)" Perhaps a better title would be "Fibers require compiler / language support to be viable"