Boost logo

Boost :

From: Christian Mazakas (christian.mazakas_at_[hidden])
Date: 2024-02-29 23:14:15

> It is up to you. I think Zach would appreciate knowing if there was a
> significant performance issue with the library.

Fwiw, there is a dramatic performance penalty to using this library and I
couldn't believe it.

I copy-pasted the JSON example from the Parser repo and then did an
informal comparison
to Boost.JSON.

For one, Boost.JSON should just export a proper CMake target like all the
other compiled Boost

And then two, these were my findings:
    â¯ ./__build__/test/json_bench
    took: 1037ms
    parse successful! 1
    took: 1ms
    parse successful! 1


I'm running all of this on a 3.6 GHz 12 core with 32 GB of RAM. I'm
honestly shocked that
it takes Boost.JSON roughly 1ms whereas it takes roughly 1000x that with

I will note this, I did have to increase the recursion limit so I'm
thinking this is actually more or
less a fault in the implementation of the recursive parsing rules in
Parser. Either way, this is 112%
worth investigating and I'd almost recommend halting acceptance until we
sort this out.

- Christian

Boost list run by bdawes at, gregod at, cpdaniel at, john at