News for hackers. Stuff that matters.
Re:PyPy's New JSON Parser by bjoli on Tuesday October 08, 2019 @11:18AM (#21193207)
I have had pretty large speedups in the past when switching JSON implementations. About 5x. It doesn't matter much when the times are 0.2 Vs 1s, but when you are working with a couple of MB of JSON the difference will definitely be noticeable.

Python's STDlib is nice, but rarely spectacular. An old naive CSV parser I wrote for Chicken scheme (using a simple state machine) beat python's C-based one.

Re:PyPy's New JSON Parser by acdha on Tuesday October 08, 2019 @11:34AM (#21193408)
> Python's STDlib is nice, but rarely spectacular. An old naive CSV parser I wrote for Chicken scheme (using a simple state machine) beat python's C-based one.

The stdlib is also conservative: I've run into quite a few cases where someone had reported huge gains until they realized they weren't properly handling escaping, Unicode, etc. and once updated the gap narrowed considerably.

Re:PyPy's New JSON Parser by ehsankia on Tuesday October 08, 2019 @11:30AM (#21193368)
You're basically agreeing with the above, and I have experienced the same. The only place where this makes a difference is when the JSON file is in MBs. For smaller file, it's not really worth the extra library.
Re:PyPy's New JSON Parser by IanCal on Tuesday October 08, 2019 @05:09PM (#21197291)
Depends on how many of the small docs you deal with, I see useful differences on small documents because I process reasonable amounts of them. A 10s change on a million docs for just decoding for a single library is easily worth it for me.