News for hackers. Stuff that matters.
Re:Four days of Go by jstarks on Wednesday April 22, 2015 @09:03PM (#9424465)
Do you have any resources demonstrating that JSON parsing in Go is slow?
Re:Four days of Go by stock_toaster on Wednesday April 22, 2015 @11:03PM (#9424801)
Here are a few google results:

* http://erickt.github.io/blog/2014/11/03/performance/ and http://erickt.github.io/blog/2014/11/11/benchmarks/

* https://github.com/ugorji/go-codec-bench

* https://github.com/golang/go/issues/5683

In my own testing it was faster (even with ffjson) to pre-clean my data in cpython or pypy, and then emit some intermediary format (like capnproto) for the go code to consume. I was parsing huge files full of lots of non-uniform json with many formats.

For most use cases though, the fact that json is "slow" is probably not a huge factor, as network IO or something else is likely the gating factor. For those uncommon cases though, I wish the native json lib in Go was faster.