jsplit
json-buffet
| jsplit | json-buffet | |
|---|---|---|
| 2 | 2 | |
| 59 | 0 | |
| - | - | |
| 10.0 | 3.0 | |
| over 1 year ago | about 1 year ago | |
| Go | C++ | |
| Apache License 2.0 | 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.
jsplit
-
Show HN: Up to 100x Faster FastAPI with simdjson and io_uring on Linux 5.19
Regarding the hard way, this little utility does a great job of splitting larger than memory JSON documents into collections of NDJSON files:
https://github.com/dolthub/jsplit
- [OC] The ridiculously absurd amount of pricing data that insurance companies just publicly dumped
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 $$$.
What are some alternatives?
data-analysis
japronto - Screaming-fast Python 3.5+ HTTP toolkit integrated with pipelining HTTP server based on uvloop and picohttpparser.
JsonReader - A JSON pull parser for PHP
semi_index - Implementation of the JSON semi-index described in the paper "Semi-Indexing Semi-Structured Data in Tiny Space"
json_benchmark - Python JSON benchmarking and "correctness".
is2 - embedded RESTy http(s) server library from Edgio
simdjson-go - Golang port of simdjson: parsing gigabytes of JSON per second
reddit_mining
price-transparency-guide - The technical implementation guide for the tri-departmental price transparency rule.
msgspec - A fast serialization and validation library, with builtin support for JSON, MessagePack, YAML, and TOML
Apache Arrow - Apache Arrow is a multi-language toolbox for accelerated data interchange and in-memory processing