3 ms·
Your benchmark results look very different from that of the web framework benchmark: http://www.techempower.com/benchmarks/#section=data-r7&hw=i7&test=json htt
by continuations 13y ago
Your benchmark results look very different from that of the web framework benchmark:
http://www.techempower.com/benchmarks/#section=data-r7&hw=i7&test=json http://www.techempower.com/benchmarks/#section=data-r7&hw=i7...
In that benchmark Go's JSON performance is almost 3x higher than that of Node.
Any reasons why there's such a big difference?
- optymizer 13y agoI think it's because they're measuring the rate at which Node.js and Go receive requests, process json, and reply as a single metric. I measured the speed with which Go and Node.js decode/encode JSON, i.e. there is no network and web server involved, just json.Marshal()/json.Unmarshal() vs JSON.parse()/JSON.stringify() I benchmarked the web server speed separately.