You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started work on what is turning out to be a fairly intensive effort to generate high quality quantitative json benchmarks with graphs, tables, and multiple statistical analyses.
I'm currently working on the code as a PR to ujson: ultrajson/ultrajson#542 but its getting involved so it might make sense to target it as a standalone repo.
Adding simdjson to my current benchmarks shows an interesting (and expected) result: the value of SIMD kicks in when the data gets large:
(Notice the red line in the left "loads" graph)
For dumps, because pysimdjson does not wrap the "dumps" and just uses "json.dumps", we get a line that maps almost exactly on top of the "json" line.
I'm writing this issue as an attempt to gauge interest in integrating my work here instead of "ujson" itself (or making yet another json benchmarking repo).
The text was updated successfully, but these errors were encountered:
I've started work on what is turning out to be a fairly intensive effort to generate high quality quantitative json benchmarks with graphs, tables, and multiple statistical analyses.
I'm currently working on the code as a PR to ujson: ultrajson/ultrajson#542 but its getting involved so it might make sense to target it as a standalone repo.
Adding simdjson to my current benchmarks shows an interesting (and expected) result: the value of SIMD kicks in when the data gets large:
(Notice the red line in the left "loads" graph)
For dumps, because pysimdjson does not wrap the "dumps" and just uses "json.dumps", we get a line that maps almost exactly on top of the "json" line.
I'm writing this issue as an attempt to gauge interest in integrating my work here instead of "ujson" itself (or making yet another json benchmarking repo).
The text was updated successfully, but these errors were encountered: