3 ms·
All I am saying is that the 'fastest' json libs all do comparisons against other 'fastest' json libs. I'd expect any other json lib trying to be faster to do t
by latchkey 5y ago
All I am saying is that the 'fastest' json libs all do comparisons against other 'fastest' json libs.
I'd expect any other json lib trying to be faster to do those same comparisons and not produce arguably clickbait "55% faster" titles since your library isn't really that much faster than goccy.
Pick the ones that match (dynamic) to compare against.
- eatonphil 5y agoIf you're not a fan of the blog post that's cool. But I posted the blog post (and wrote the post in the first place) rather than a Show HN link to the project itself because I thought the process was worth showing as much as the result.
- mh- 5y ago> I thought the process was worth showing as much as the result it was, thanks for sharing.
- strangeattractr 5y agoI enjoyed reading it, as someone who writes a lot of go but hasn't done any profiling of code.
- kodah 5y agoI've known for some time that the JSON process of marshaling is expensive in Go; this post illuminates why and taught me how to test these kinds of things myself. It's excellent and I appreciate you sharing your methodology.