simdjson-go VS go-json

Speaking of Go, there's a simdjson implementation for golang too:

> Performance wise, simdjson-go runs on average at about 40% to 60% of the speed of simdjson. Compared to Golang's standard package encoding/json, simdjson-go is about 10x faster.

I haven't tried it yet but I don't really need that speed.

https://github.com/minio/simdjson-go

I agree. For performance-sensitive situations, C/C++ or Rust is the only choice. However, many developers choose Go or other languages for engineering efficiency. A typical use case of SIMD in Go is simdjson-go. Besides, there are plenty of bindings and ports of simdjson. "Other languages" developers also need performance improvement from native instructions such as SIMD.

I suggest to use a streaming library to parse your file. Like jstream or simdjson-go

You can also try comparing with https://github.com/minio/simdjson-go. It does use a different API, however, would be good to compare nevertheless.

For go -> you can actually get away with the standard json encoding package. Or if you want a slightly better one, I prefer goccy/go-json

Someone made a benchmark of serialization libraries in go [1], and I was surprised to see gobs is one of the slowest ones, specially for decoding. I suspect part of the reason is that the API doesn't not allow reusing decoders [2]. From my explorations it seems like both JSON [3], message-pack [4] and CBOR [5] are better alternatives.

By the way, in Go there are a like a million JSON encoders because a lot of things in the std library are not really coded for maximum performance but more for easy of usage, it seems. Perhaps this is the right balance for certain things (ex: the http library, see [6]).

There are also a bunch of libraries that allow you to modify a JSON file "in place", without having to fully deserialize into structs (ex: GJSON/SJSON [7] [8]). This sounds very convenient and more efficient that fully de/serializing if we just need to change the data a little.

--

1: https://github.com/alecthomas/go_serialization_benchmarks

2: https://github.com/golang/go/issues/29766#issuecomment-45492...

--

3: https://github.com/goccy/go-json

4: https://github.com/vmihailenco/msgpack

5: https://github.com/fxamacker/cbor

--

6: https://github.com/valyala/fasthttp#faq

--

7: https://github.com/tidwall/gjson

8: https://github.com/tidwall/sjson

Drop-in replacement for the stdlib JSON package: https://github.com/goccy/go-json

go stdlib json encoding/decoding is incredibly slow, not sure for how much longer because there are drop in replacements now that I think are just as strict and feature parity.

3rd party JSON libraries could help if you were comparing JSON. https://github.com/goccy/go-json

However, I understand the code that is generated is super optimized. For example, rather than use a router, it does a static code generated router. Rather than use goccy/go-json, it does manual marshalling.

Minimal dependencies: julienschmidt/httprouter and goccy/go-json

I suggested using https://github.com/goccy/go-json at my work, since its a drop in replacement for the standard lib, but there are people who apprehensive. In my opinion the performance gains are significant to justify adoption. But I'd like your input.

go-json for encoding/decoding