Hacker News Reader

Comment by nemothekid | Hacker News Reader

simdjson is listed thought.

It is mentioned here: https://github.com/bytedance/sonic/blob/a577eafc253adb943924..., but it isn't included in the benchmarks graphs. Seems this repo is specifically focused on Golang and isn't necessarily motivated by being the fastest JSON [de]serializer on the planet.

There is this one though: https://github.com/minio/simdjson-go

EDIT: Apologies, simdjson-go is included in the benchmarks and discussed as well.

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.

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.

the graphs show rate not time

If someone runs at a.. 'higher' rate (m/s) than someone else, is it not right to say that they are faster?

Yes. 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.

Oh right yes sorry I didn't really tie up the discussion to the graphs (or lacked caffeine or something!).

Right, 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.

Reply on news.ycombinator.com