I just submitted a PR to improve performances of the Go/ActionLoop runtime while being the less invasive possible.
I am keeping the current design and I have not changed approach: there is still child process fed by the HTTP server on standard input with output on file descriptor 3. I am still using the standard http server (not the fast HTTP server). On the converse, I removed all the goroutines. They do not play well with external processes. Instead, I am using the classical technique of suspending on reading the standard input is fast to commute to the child process/ I reached in my tests around 1150 requests/second (a bit worse than the nodejs but I think decent). It is possible to further improve performances up to 1500 but I need to abandon the actionloop model and run an action with an independent server, so for now I am not doing anything like this, -- Michele Sciabarra mich...@sciabarra.com
