Whoa, thanks. 368, huh? That's pretty impressive given the 1.9Ghz clock speed... By coincidence, the 'twitter.json' file was the one I was using as my slender data point.
Do note that at this stage the benchmark is so preliminary as to be largely meaningless - I haven't really done much more than eyeball the results. But as a preliminary data point, that seems to be a stronger showing clock-for-clock than the eMag one.
let me know if you want this data in github. Just testing our overclocking bring cpu clock up to 2.4Ghz and DDR to 3200
Also building with gcc 8.2 not I needed to change -march=native to -march=armv8-a+crypto
Min: 0.00111424 bytes read: 631514 Gigabytes/second: 0.566768
./parse jsonexamples/twitter.json
Min: 0.00171284 bytes read: 631514 Gigabytes/second: 0.368695