[HN Gopher] JSON Parsing: Intel Sapphire Rapids versus AMD Zen 4
       ___________________________________________________________________
        
       JSON Parsing: Intel Sapphire Rapids versus AMD Zen 4
        
       Author : mfiguiere
       Score  : 34 points
       Date   : 2024-02-09 19:59 UTC (3 hours ago)
        
 (HTM) web link (lemire.me)
 (TXT) w3m dump (lemire.me)
        
       | jauntywundrkind wrote:
       | As always, love these random rundowns. The matrix of JSON library
       | x task is neat to see, feels much more comprehensive than just
       | running a couple straight head to heads!
       | 
       | I do wish there was a newer compiler in use. GCC 11 was from
       | March 2021. Using a nearly 3 year old compiler feels like it's
       | leaving hard work & tuning on the table, isnt indicative of what
       | these professors might be capable of.
        
       | unglaublich wrote:
       | Woa, didn't know my favorite C++ json library is _that_ slow!
        
       | olliej wrote:
       | It's interesting to see the performance numbers for JSON parsing
       | in the context of parsing performance specifically. I guess this
       | is largely a domain specific detail, as my experience was in the
       | context of JS engines.
       | 
       | For JSC at least the costs of allocating and constructing the JS
       | object graph rapidly dwarf the cost of the parsing itself for any
       | non-trivial JSON structure (though parsing JSON is still
       | sufficiently fast relative to actual JS that there's still a
       | significant win for all JS execution in JSC to start with an
       | attempt to parse the input as a slightly extended JSON syntax,
       | due to the wonders of JSONP and people still using eval for json
       | parsing).
        
       ___________________________________________________________________
       (page generated 2024-02-09 23:01 UTC)