4 ms·
If you read the original blog post on http://blog.safariflow.com/2013/02/22/go-as-an-alternative-to-node-js-for-very-fast-servers/ http://blog.safariflow.com/20
by munimkazia 13y ago
If you read the original blog post on http://blog.safariflow.com/2013/02/22/go-as-an-alternative-to-node-js-for-very-fast-servers/ http://blog.safariflow.com/2013/02/22/go-as-an-alternative-t..., one of the commentators actually attempted the comparison between node.js and go, and his results for node.js was significantly faster.
- axaxs 13y agoGo version 1.1 was more than a significant increase in net handling speed.
- bhauer 13y agoNot only that, but although the particular test described in the linked blog post did not include database connectivity, we saw a massive increase in database performance in 1.1 versus 1.0.2 due to a fix in the sql package [1]. That was back in Round 4 of our project [2]. Just something to be aware of if anyone reading has Go 1.0.2 installed and has not yet upgraded. 1.1 is worth the upgrade. [1] https://code.google.com/p/go/source/detail?r=45c12efb46 https://code.google.com/p/go/source/detail?r=45c12efb46 [2] http://www.techempower.com/blog/2013/05/02/frameworks-round-4/ http://www.techempower.com/blog/2013/05/02/frameworks-round-...
- bhauer 13y agoThanks for the link to the original. Perhaps "February 22, 2013" should be identified in the title here? That explains the use of Go 1.0.2.