Re: New JSON library from the maker of Beast!

From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2019-10-22 17:49:20

On Tue, Oct 22, 2019 at 10:18 AM Mateusz Loskot via Boost
<boost_at_[hidden]> wrote:
> Does it mean you have run it under Milo's nativejson-benchmark?

I tried to integrate it into that benchmark but to be honest, that
project looks like a hot mess. I don't have the resources to try to
get my library working with it.

> Can you post the results?

I have the results from a simple benchmarking program that I wrote,
which parses a bunch of random JSON. There are two data sets, a small
one and a big one:

small data set:
rapidjson parse 55952763 bytes in 230ms
rapidjson parse 55952763 bytes in 229ms
rapidjson parse 55952763 bytes in 228ms
nlohmann parse 55952763 bytes in 514ms
nlohmann parse 55952763 bytes in 514ms
nlohmann parse 55952763 bytes in 533ms
Boost.JSON parse 55952763 bytes in 234ms
Boost.JSON parse 55952763 bytes in 233ms
Boost.JSON parse 55952763 bytes in 233ms

large data set:
rapidjson parse 488889121 bytes in 1793ms
rapidjson parse 488889121 bytes in 1791ms
rapidjson parse 488889121 bytes in 1789ms
nlohmann parse 488889121 bytes in 3921ms
nlohmann parse 488889121 bytes in 3942ms
nlohmann parse 488889121 bytes in 3965ms
Boost.JSON parse 488889121 bytes in 1754ms
Boost.JSON parse 488889121 bytes in 1761ms
Boost.JSON parse 488889121 bytes in 1764ms

The benchmark program is here:
<https://github.com/vinniefalco/json/blob/master/bench/bench.cpp>

I will likely expand on it to measure more things and report the
results in the documentation (a work in progress).

> I have not found enough time to pull your library in.

I still have a bit of work to do with the treatment of floating point
numbers, and there are a couple of bugs with the handling of utf code
points. Those will be done very soon.

Thanks