Description
See what happens when imposing memory limits. Perhaps a 6MB soft limit, using GOMEMLIMIT and --max-old-space-size and a 10MB hard limit on the docker container. This might put some of what Go is doing under the hood in perspective. If you do this you'll notice that you only lose slight performance with Go but Node will hardly get through a few thousand requests before OOM. Point of this is you can set any arbitrary limit you want on things to hamstring the performance of any application.
This sort of testing is really dangerous because new developers that don't know how to look at the whole situation believe these types of tests and then I have to set them straight at work, which is how I found you... Nobody is purposely hamstringing themselves like this in production so what does this prove... It proves that if you put random limitations on different programming languages you get skewed results. That isn't a big surprise I hope to anyone.