json-buffet
yyjson
json-buffet | yyjson | |
---|---|---|
2 | 5 | |
0 | 2,893 | |
- | - | |
3.0 | 7.4 | |
about 1 year ago | 15 days ago | |
C++ | C | |
MIT License | 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.
json-buffet
-
Analyzing multi-gigabyte JSON files locally
And here's the code: https://github.com/multiversal-ventures/json-buffet
The API isn't the best. I'd have preferred an iterator based solution as opposed to this callback based one. But we worked with what rapidjson gave us for the proof of concept.
-
Show HN: Up to 100x Faster FastAPI with simdjson and io_uring on Linux 5.19
Ha! Thanks to you, Today I found out how big those uncompressed JSON files really are (the data wasn't accessible to me, so i shared the tool with my colleague and he was the one who ran the queries on his laptop): https://www.dolthub.com/blog/2022-09-02-a-trillion-prices/ .
And yep, it was more or less they way you did with ijson. I found ijson just a day after I finished the prototype. Rapidjson would probably be faster. Especially after enabling SIMD. But the indexing was a one time thing.
We have open sourced the codebase. Here's the link: https://github.com/multiversal-ventures/json-buffet . Since this was a quick and dirty prototype, comments were sparse. I have updated the Readme, and added a sample json-fetcher. Hope this is more useful for you.
Another unwritten TODO was to nudge the data providers towards a more streaming friendly compression formats - and then just create an index to fetch the data directly from their compressed archives. That would have saved everyone a LOT of $$$.
yyjson
- FLaNK Stack Weekly for 07August2023
- yyjson: A high performance C JSON library
-
Show HN: Up to 100x Faster FastAPI with simdjson and io_uring on Linux 5.19
How does yyjson[0] compare to simdjson? Their benchmarks suggest it could be a positive.
[0] https://github.com/ibireme/yyjson
-
Why is my program segfaulting?
Also I am using these libraries: JSON: https://github.com/ibireme/yyjson Networking: https://curl.se/libcurl/
-
How to parse JSON in C ?
If you need speed, by far yyjson. But it sounds like you probably don't need speed, so the other suggestions are likely better.
What are some alternatives?
japronto - Screaming-fast Python 3.5+ HTTP toolkit integrated with pipelining HTTP server based on uvloop and picohttpparser.
json-c - https://github.com/json-c/json-c is the official code repository for json-c. See the wiki for release tarballs for download. API docs at http://json-c.github.io/json-c/
semi_index - Implementation of the JSON semi-index described in the paper "Semi-Indexing Semi-Structured Data in Tiny Space"
cJSON - Ultralightweight JSON parser in ANSI C
is2 - embedded RESTy http(s) server library from Edgio
JSMN - Jsmn is a world fastest JSON parser/tokenizer. This is the official repo replacing the old one at Bitbucket
reddit_mining
parson - Lightweight JSON library written in C.
json_benchmark - Python JSON benchmarking and "correctness".
ultrajson - Ultra fast JSON decoder and encoder written in C with Python bindings
Apache Arrow - Apache Arrow is a multi-language toolbox for accelerated data interchange and in-memory processing
gorilla-cli - LLMs for your CLI