go_serialization_benchmarks icon indicating copy to clipboard operation
go_serialization_benchmarks copied to clipboard

Benchmarks of Go serialization methods

Results 18 go_serialization_benchmarks issues
Sort by recently updated
recently updated
newest added

Please add benchmark for gjson (https://github.com/tidwall/gjson), it seems super fast.

As golang protobuf readme said: ``` It has been superseded by the google.golang.org/protobuf module, which contains an updated and simplified API, support for protobuf reflection, and many other improvements. We...

Go Protobuf has a new major version: https://blog.golang.org/protobuf-apiv2. It would be nice to add it to the benchmarks for a comparison.

Hello, It would be nice to have _Bebop_ **message** and **union** definition(s) benchmarked as well. In practice, I find myself relying on **message** and **union** more often than bare **struct**...

Hi, guys! Do you remember [#120](https://github.com/alecthomas/go_serialization_benchmarks/issues/120)? I implemented something similar, but in a separate [project](https://github.com/ymz-ncnk/go-serialization-benchmarks). And we could merge both projects into one. As a variant, we could create an...

Instead of relying on a makefile to generate bindings for the serializers that rely on code generation, we should move those instructions into each serializer package, so that it is...

Based on my tests high order algorithms often (not always) have more chance than others. I developed two scripts benchmarks.sh and genreport_test.sh that runs "go test" per algorithm separately and...