3 ms·
Just another case where a library tests and publishes results for all competing libraries slower than it, but none faster. cough simdjson [1] cough --- [1] ht
by BeeOnRope 5y ago
Just another case where a library tests and publishes results for all competing libraries slower than it, but none faster. cough simdjson [1] cough
---
[1] https://github.com/simdjson/simdjson https://github.com/simdjson/simdjson
- deleted 5y ago[deleted]
- nemothekid 5y agosimdjson is listed thought.
- memco 5y agoIt is mentioned here: https://github.com/bytedance/sonic/blob/a577eafc253adb943924f74f310509c6c80bd3f3/INTRODUCTION.md#research 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.
- craigching 5y agoThere is this one though: https://github.com/minio/simdjson-go https://github.com/minio/simdjson-go EDIT: Apologies, simdjson-go is included in the benchmarks and discussed as well.
- BeeOnRope 5y agoWell 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.
- TkTech 5y agoA 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.