>I cheated in one application and pinned the go process to each cpu and lied to Go and told it there was only one CPU but then you loose all the cool features o

>I cheated in one application and pinned the go process to each cpu and lied to Go and told it there was only one CPU but then you loose all the cool features of channels etc.. That helped some but a Nginx/LuaJIT implementation of the same solution still crushed it on the same box, identical workload. If your primary motivation for using Go is lightweight concurrency, it has been developed for Lua, though in fairness not as extensively as goroutines: http://github.com/askyrme/luaproc http://github.com/askyrme/luaproc http://www.jucs.org/jucs_14_21/exploring_lua_for_concurrent/jucs_14_21_3556_3572_skyrme.pdf http://www.jucs.org/jucs_14_21/exploring_lua_for_concurrent/...