4 ms·
A port of simdjson, simdjson-go, is in the benchmark graphs. It seems to be too fast to be visible in most of the graphs.
by TkTech 5y ago
A port of simdjson, simdjson-go, is in the benchmark graphs. It seems to be too fast to be visible in most of the graphs.
- skavi 5y agothe graphs show rate not time
- OJFord 5y agoIf someone runs at a.. 'higher' rate (m/s) than someone else, is it not right to say that they are faster?
- tzs 5y agoYes. But on a bar graph showing rate taller bars mean faster, but on a bar graph showing time to complete a task taller bars mean slower. 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.
- OJFord 5y agoOh right yes sorry I didn't really tie up the discussion to the graphs (or lacked caffeine or something!).
- dr_zoidberg 5y agoRight, they show MB/s of parsed JSON, and it definitely surprised me: simdjson-go is among the slowest! It looks like there's something fishy going on there, as it is _orders of magnitude_ slower that vanilla simdjson.