go_serialization_benchmarks
go-json
go_serialization_benchmarks | go-json | |
---|---|---|
8 | 24 | |
1,527 | 2,778 | |
- | - | |
4.4 | 3.2 | |
12 days ago | 7 days ago | |
Go | Go | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go_serialization_benchmarks
-
Rob Pike: Gobs of data (2011)
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
-
Introducing Tempo: low latency, cross-platform, end-to-end typesafe APIs
The bebop definition specifies fixed-width types inside a struct. The format of structs cannot be changed, but there are efficiency gains by omitting all of the indices and header data. It's useless as the root message, but it's small and fast for a benchmark.
-
mus-go - the fastest Golang serializer today
Hey everyone! Let me introduce you to mus-go - the fastest Golang serializer today. If you look at benchmarks (https://github.com/alecthomas/go_serialization_benchmarks), you can see that it could be almost twice as fast as its closest "competitor":
-
What is the fastest way to encode the arbitrary struct into bytes?
This might be of interest: https://github.com/alecthomas/go_serialization_benchmarks
- 80x improvements in caching by moving from JSON to gob
-
gRPC Is Easy to Misconfigure
The protobuf vs msgpack benchmarks are not too bad. Msgpack performs very decently.
https://github.com/alecthomas/go_serialization_benchmarks
-
Bebop encoding in Go
Maybe submit a PR against https://github.com/alecthomas/go_serialization_benchmarks? That covers a ton of serialization formats already, so adding your library would be cool and avoid wheel reinvention.
go-json
-
API: Go, .NET, Rust
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
-
Rob Pike: Gobs of data (2011)
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
-
Data storage speed comparisons?
Drop-in replacement for the stdlib JSON package: https://github.com/goccy/go-json
-
Go is 2-3 times slower than JS in a similar code. What makes Go slow in this specific code?
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.
-
Go with Chi has more ram consumption and less req/s than Koa or Fastify
3rd party JSON libraries could help if you were comparing JSON. https://github.com/goccy/go-json
-
ogen: spec-first OpenAPI v3 codegen for Go
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.
-
japi is a JSON HTTP API go library with generics
Minimal dependencies: julienschmidt/httprouter and goccy/go-json
-
Using a json lib other than encoding/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.
- Whats the fastest JSON unmarshaling package as of right now?
-
What are your favorite packages to use?
go-json for encoding/decoding
What are some alternatives?
bebop - bebop wire format in Go
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
encoding - Go package containing implementations of efficient encoding, decoding, and validation APIs.
easyjson - Fast JSON serializer for golang.
bebop - 🎷No ceremony, just code. Blazing fast, typesafe binary serialization.
GJSON - Get JSON values quickly - JSON parser for Go
msgpack - MessagePack is an extremely efficient object serialization library. It's like JSON, but very fast and small.
go-fuzz - Randomized testing for Go
grpc-web - gRPC for Web Clients
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
msgp - A Go code generator for MessagePack / msgpack.org[Go]
zap - Blazing fast, structured, leveled logging in Go.