I missed that fact. In that case, the author is measuring something that's completely useless. The entire advantage of Go is that it has really good multithrea

I missed that fact. In that case, the author is measuring something that's completely useless. The entire advantage of Go is that it has really good multithreaded asynchronous behavior. A benchmark that's measuring single thread performance of a task that's optimized to do well in a single thread (i.e., it doesn't actually do anything other than return static text) is entirely worthless. If you're going to be returning static text, may as well compare to Nginx, which I'm certain can return static text even faster. If you're going to be doing processing in Python, then do at least something. And run in multiple threads, since that's Go's native environment. Rating: PANTS ON FIRE. [1] [1] Not your comparison, but the original author's performance claims.