Well it wasn't in the benchmark graphs and it didn't show in Ctrl+F in the README.
Admittedly, I didn't do an exhaustive search.
Admittedly, I didn't do an exhaustive search.
The graphs are showing rate and simdjson-go has shorter bars (or nonexistent bars which suggest a quantity too low to show up at the resolution of the graphs). TkTech though the graphs were showing time and so thought they were showing that simdjson-go is very fast, which skavi is pointing out is reversed because they are showing rate.