pysimdjson
ojg
Our great sponsors
pysimdjson | ojg | |
---|---|---|
6 | 17 | |
628 | 779 | |
- | - | |
5.3 | 7.0 | |
about 2 months ago | 29 days ago | |
Python | Go | |
GNU General Public License v3.0 or later | 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.
pysimdjson
- Analyzing multi-gigabyte JSON files locally
-
I Use C When I Believe in Memory Safety
Its magic function wrapping comes at a cost, trading ease of use for runtime performance. When you have a single C++ function to call that will run for a "long" time, pybind all the way. But pysimdjson tends to call a single function very quickly, and the overhead of a single function call is orders of magnitude slower than with cython when being explit with types and signatures. Wrap a class in pybind11 and cython and compare the stack trace between the two, and the difference is startling.
-
Processing JSON 2.5x faster than simdjson with msgspec
simdjson
-
[package-find] lsp-bridge
You are aware of simdjson being available in python if you really need some json crunching, albeit json module in Python is implemented in C itself, so I don't think understand why do you think Python is slow there?
-
The fastest tool for querying large JSON files is written in Python (benchmark)
json: 113.79130696877837 ms
While `orjson`, is faster than `ujson`/`json` here, it's only ~6% faster (in this benchmark). `simdjson` and `msgspec` (my library, see https://jcristharif.com/msgspec/) are much faster due to them avoiding creating PyObjects for fields that are never used.
If spyql's query engine can determine the fields it will access statically before processing, you might find using `msgspec` for JSON gives a nice speedup (it'll also type check the JSON if you know the type of each field). If this information isn't known though, you may find using `pysimdjson` (https://pysimdjson.tkte.ch/) gives an easy speed boost, as it should be more of a drop-in for `orjson`.
-
How I cut GTA Online loading times by 70%
I don't think JSON is really the problem - parsing 10MB of JSON is not so slow. For example, using Python's json.load takes about 800ms for a 47MB file on my system, using something like simdjson cuts that down to ~70ms.
ojg
-
Interactive Examples for Learning Jq
I found Jq to be difficult to use which is why Oj, https://github.com/ohler55/ojg is based on JSONPath. There still are a lot of options but it only takes a couple of help screens to figure out what the options are.
-
Building a high performance JSON parser
You might want to take a look at https://github.com/ohler55/ojg. It takes a different approach with a single pass parser. There are some performance benchmarks included on the README.md landing page.
-
A Journey building a fast JSON parser and full JSONPath
I like the "Simple Encoding Notation" (SEN) of the underlying library: https://github.com/ohler55/ojg/blob/develop/sen.md
-
The fastest tool for querying large JSON files is written in Python (benchmark)
For me OjG (https://github.com/ohler55/ojg) has been great. I regularly use it on files that can not be loaded into memory. The best JSON file format for multiple record is one JSON document per record all in the same file. OjG doesn't care if they are on different lines. It is fast (https://github.com/ohler55/compare-go-json) and uses a fairly complete JSONPath implementation for searches. Similar to jq but using JSONPath instead of a proprietary query language.
I am biased though as I wrote OjG to handle what other tools were not able to do.
-
FX: An interactive alternative to jq to process JSON
Another alternative is the oj app (ojg/cmd/oj) which is part of https://github.com/ohler55/ojg. It relies on JSONPath for extraction and manipulation of JSON.
- Go 1.17 Release Notes
-
OjG now has a tokenizer that is almost 10 times faster than json.Decode
Check out the SEN https://github.com/ohler55/ojg/blob/develop/sen.md format. You can have the last comma or leave all of them out and it still supports compliant JSON.
I promise to add more examples but in the mean time there are the test files. The one for Unmarshal is https://github.com/ohler55/ojg/blob/develop/oj/unmashall_test.go
What are some alternatives?
orjson - Fast, correct Python JSON library supporting dataclasses, datetimes, and numpy
cysimdjson - Very fast Python JSON parsing library
ultrajson - Ultra fast JSON decoder and encoder written in C with Python bindings
Fast JSON schema for Python - Fast JSON schema validator for Python.
lupin is a Python JSON object mapper - Python document object mapper (load python object from JSON and vice-versa)
PyValico - Small python wrapper around https://github.com/rustless/valico
jsonparser - One of the fastest alternative JSON parser for Go that does not require schema
marshmallow - A lightweight library for converting complex objects to and from simple Python datatypes.
jsonic - All you need with JSON
serpy - ridiculously fast object serialization
fastjson - Fast JSON parser and validator for Go. No custom structs, no code generation, no reflection
hjson-py - Hjson for Python