This project provides a comprehensive benchmark comparing multiple JSONPath libraries implemented in the Go programming language. It aims to evaluate performance under specific scenarios and offer insights for developers choosing an appropriate library for their use case.
Results are generated using GitHub Actions to ensure consistency and automation.
The focus of the benchmark is on the cost per operation after the initial setup is complete. This means that preparatory steps, such as parsing or preloading data, are excluded from the measurements. Instead, the benchmark emphasizes scenarios involving intensive looping or query execution within the main operation.
The results may vary depending on several factors, such as the structure of the input data, the complexity of the JSONPath queries, and the specific runtime environment. For this reason, these benchmarks should be considered as a general reference and re-evaluated periodically.
The following libraries are included in this benchmark:
- AsaiYusuke/JSONPath
- ohler55/OjG
- vmware-labs/YAML JSONPath
- bhmj/JSONSlice
- Spyzhov/Abstract JSON
- oliveagle/JsonPath
- PaesslerAG/JSONPath
JSONPath:
$.store.book[0].price
Performance Summary:
This query was supported by all libraries included in the benchmark, enabling a direct performance comparison across all of them.
The fastest performance was achieved by oliveagle/JsonPath, with my library ranking second.
goos: linux
goarch: amd64
pkg: github.com/AsaiYusuke/jsonpath_benchmark
cpu: AMD EPYC 7763 64-Core Processor
Benchmark1_oliveagle_JsonPath-4 19118167 63.72 ns/op 0 B/op 0 allocs/op
Benchmark1_AsaiYusuke_JSONPath-4 8535836 122.8 ns/op 24 B/op 2 allocs/op
Benchmark1_ohler55_OjG_jp-4 3072985 397.1 ns/op 1040 B/op 2 allocs/op
Benchmark1_PaesslerAG_JSONPath-4 2654620 457.3 ns/op 208 B/op 7 allocs/op
Benchmark1_vmware_labs_YAML_JSONPath-4 1302009 915.4 ns/op 400 B/op 25 allocs/op
Benchmark1_bhmj_JSON_Slice-4 814838 1442 ns/op 24 B/op 1 allocs/op
Benchmark1_Spyzhov_Abstract_JSON-4 595665 1868 ns/op 760 B/op 35 allocs/op
PASS
ok github.com/AsaiYusuke/jsonpath_benchmark 10.228s
JSONPath:
$..book[?(@.price > $.store.bicycle.price)]
Performance Summary:
This query involves more complex syntax, and only a subset of the libraries were able to process it. Among these, my library demonstrated the best performance.
goos: linux
goarch: amd64
pkg: github.com/AsaiYusuke/jsonpath_benchmark
cpu: AMD EPYC 7763 64-Core Processor
Benchmark2_AsaiYusuke_JSONPath-4 655096 1832 ns/op 240 B/op 9 allocs/op
Benchmark2_ohler55_OjG_jp-4 294267 3640 ns/op 5368 B/op 25 allocs/op
Benchmark2_vmware_labs_YAML_JSONPath-4 233802 4913 ns/op 4528 B/op 141 allocs/op
Benchmark2_bhmj_JSON_Slice-4 70894 16851 ns/op 1816 B/op 43 allocs/op
Benchmark2_Spyzhov_Abstract_JSON-4 57480 19450 ns/op 7160 B/op 279 allocs/op
PASS
ok github.com/AsaiYusuke/jsonpath_benchmark 6.241s
This benchmark highlights significant performance differences among popular JSONPath libraries. Developers can use these results as a reference when selecting a library, particularly when performance is critical. For real-world use, consider running benchmarks tailored to your specific datasets and queries.