[HN Gopher] WASM compression benchmarks and the cost of missing ...
       ___________________________________________________________________
        
       WASM compression benchmarks and the cost of missing compression
       APIs
        
       Author : comagoosie
       Score  : 19 points
       Date   : 2023-02-01 11:23 UTC (1 days ago)
        
 (HTM) web link (nickb.dev)
 (TXT) w3m dump (nickb.dev)
        
       | miohtama wrote:
       | Related to compressing data before storing on SSD:
       | 
       | Blosc - faster than memcpy()
       | 
       | https://github.com/Blosc/c-blosc
       | 
       | On right circumstances Blosc is so fast that even speed ups
       | reading data from RAM (read less, decompress in L1 and L2 caches)
        
       | dorfsmay wrote:
       | Note that both the x and the y axis for Chrome vs Firefox are
       | significantly different.
        
       | modeless wrote:
       | The web platform could really use zstd everywhere. As a content
       | encoding for HTTP, and as an API available to JS/wasm. It's
       | really clumsy to use a wasm version of zstd in a JS application
       | because it's hard to get data in and out of wasm efficiently.
        
         | capableweb wrote:
         | I'd be happy if just CompressionStream could be available as an
         | API in all browsers already, so I could at least use gzip...
         | Once available, I'm guessing zstd could be easier to add in
         | later, or lz4.
        
       | zokier wrote:
       | just for scale it would have been fun to see zstd/lz4 native
       | (=non-wasm) performance
        
       ___________________________________________________________________
       (page generated 2023-02-02 23:01 UTC)