serde_json_borrow
json-benchmark
serde_json_borrow | json-benchmark | |
---|---|---|
2 | 12 | |
68 | 169 | |
- | 2.4% | |
5.1 | 4.8 | |
8 months ago | about 1 month ago | |
Rust | C++ | |
MIT License | Apache License 2.0 |
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.
serde_json_borrow
-
Serde Json vs Rapidjson (Rust vs C++)
The rust version also measures allocation overhead by a lot. The c++ version uses “insitu” parsing which means it prefers “borrowing” over allocating new structures (like for strings). You might wanna add https://github.com/PSeitz/serde_json_borrow to your comparison, iiuc it supports a “Value” which borrows from the input. If that’s too slow for you too, you might wanna take a look at an alternative json parser, eg. https://crates.io/crates/simd-json.
- serde_json_borrow: Faster JSON deserialization by reducing allocations via parsing &'ctx str into Value<'ctx>
json-benchmark
-
Do You Know How Much Your Computer Can Do in a Second?
I don’t really understand what this is trying to prove:
- you don’t seem to specify the size of the input. This is the most important omission
- you are constructing an optimised representation (in this case, strict with fields in the right places) instead of a generic ‘dumb’ representation that is more like a tree of python dicts
- rust is not a ‘moderately fast language’ imo (though this is not a very important point. It’s more about how optimised the parser is, and I suspect that serde_json is written in an optimised way, but I didn’t look very hard).
I found[1], which gives serde_json to a dom 300-400MB/s on a somewhat old laptop cpu. A simpler implementation runs at 100-200, a very optimised implementation gets 400-800. But I don’t think this does that much to confirm what I said in the comment you replied to. The numbers for simd json are a bit lower than I expected (maybe due to the ‘dom’ part). I think my 50MB/a number was probably a bit off but maybe the python implementation converts json to some C object and then converts that C object to python objects. That might half your throughput (my guess is that this is what the ‘strict parse’ case for rustc_serialise is roughly doing).
[1] https://github.com/serde-rs/json-benchmark
-
Serde Json vs Rapidjson (Rust vs C++)
But the code OP posted deserializes JSON without knowing anything about the structure, which is known to be slow in serde-json and doesn't appear to be the focus for the library. The json and json-deserializer crates should perform much better in that scenario.
- Good example of high performance Rust project without unsafe code?
- I'm a veteran C++ programmer, what can Rust offer me?
-
Rust is just as fast as C/C++
Of course that doesnt mean that in practice the available libraries are as optimized. Did you try actix? It tends to be faster than rocket. Also json-rust and simd-json are usually faster than serde-json, when you don't deserialize a known structure. Here are some benchmarks: https://github.com/serde-rs/json-benchmark
-
Lightweight template-based parser build system. Simple prototyping. Comfortable debugging. Effective developing.
The data for the test is taken from here: https://github.com/serde-rs/json-benchmark/tree/master/data
-
Performance of serde js value conversion and reference types
Here are some benchmarks https://github.com/serde-rs/json-benchmark
-
Serde zero-copy benchmarks?
I found two projects: * https://github.com/djkoloski/rust_serialization_benchmark - doesn't use Serde zero copy * https://github.com/serde-rs/json-benchmark - has copy vs borrowed, but the results were the same for both, so something's off there
-
Android Developers Have A Tough Life
Rust has a good enough standard library (I’d say comparable to C++), that you don’t really need packages for a lot of stuff. Most of my projects have 1 or 2 dependencies. Most of the time I am pulling in a JS parser (serde) and a parallelization library (rayon). These are both high performance libraries that make writing very fast (serde can handle 850 MB/s on a 5 year old laptop cpu per their benchmarks). Rayon is one of the best parallelism libraries I’ve worked with.
What are some alternatives?
pikkr - JSON parser which picks up values directly without performing tokenization in Rust
rust_serialization_benchmark - Benchmarks for rust serialization frameworks
json_typegen - Tools and libraries to create types for Rust, Kotlin, TypeScript and Python from JSON samples
hjson-rust for serde - Hjson for Rust
simd-json - Rust port of simdjson
hyperjson - 🐍 A hyper-fast Python module for reading/writing JSON data using Rust's serde-json.
MessagePack - MessagePack serializer implementation for Java / msgpack.org[Java]
json - Strongly typed JSON library for Rust
safety-dance - Auditing crates for unsafe code which can be safely replaced
image-png - PNG decoding and encoding library in pure Rust
cv - Rust CV mono-repo. Contains pure-Rust dependencies which attempt to encapsulate the capability of OpenCV, OpenMVG, and vSLAM frameworks in a cohesive set of APIs.
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library