Re:A Journey building a fast JSON parser and full JSONPath, ...
by peterohler on Sunday July 05, 2020 @10:15AM
(#23738802)
What I tried was getting each member of a parsed/loaded doc vs a single element. If I was using the library incorrectly my apologies. When I put the code up maybe you can give suggestions on how to make it more realistic. I will gladly retract my performance statement if it turns out I was using your library incorrectly.
[ Parent
| on HN ]
Re:A Journey building a fast JSON parser and full JSONPath, ...
by peterohler on Sunday July 05, 2020 @11:11AM
(#23739251)
Benchmarks have been added at https://github.com/ohler55/ojc/blob/master/test/simdbench/RE...
Re:A Journey building a fast JSON parser and full JSONPath, ...
by tjko on Sunday July 05, 2020 @12:30PM
(#23739875)
Do you not need to specify optimization flags when compiling?
Re:A Journey building a fast JSON parser and full JSONPath, ...
by peterohler on Sunday July 05, 2020 @12:50PM
(#23740037)
The -O3 optimization is just an optimization. It made a 1% difference in performance. It's just something I had in the Makefile I copied.