News for hackers. Stuff that matters.
Re:New JSON encoder for Haskell that is up to 3x faster than... by nikita-volkov on Monday October 19, 2020 @07:44AM (#24825401)
I've updated the benchmarks to include "buffer-builder". It's not very different from "aeson".

    jsonifier/1kB          mean 2.087 μs  ( +- 260.0 ns  )
    jsonifier/6kB          mean 12.33 μs  ( +- 222.2 ns  )
    jsonifier/60kB         mean 118.3 μs  ( +- 1.991 μs  )
    jsonifier/600kB        mean 1.270 ms  ( +- 38.92 μs  )
    jsonifier/6MB          mean 20.53 ms  ( +- 1.042 ms  )
    jsonifier/60MB         mean 194.9 ms  ( +- 15.04 ms  )
    aeson/1kB              mean 6.542 μs  ( +- 199.2 ns  )
    aeson/6kB              mean 31.25 μs  ( +- 494.5 ns  )
    aeson/60kB             mean 261.7 μs  ( +- 8.044 μs  )
    aeson/600kB            mean 3.395 ms  ( +- 114.6 μs  )
    aeson/6MB              mean 30.71 ms  ( +- 701.0 μs  )
    aeson/60MB             mean 277.1 ms  ( +- 4.776 ms  )
    lazy-aeson/1kB         mean 6.423 μs  ( +- 83.69 ns  )
    lazy-aeson/6kB         mean 30.74 μs  ( +- 607.0 ns  )
    lazy-aeson/60kB        mean 259.1 μs  ( +- 4.890 μs  )
    lazy-aeson/600kB       mean 2.511 ms  ( +- 18.71 μs  )
    lazy-aeson/6MB         mean 24.92 ms  ( +- 95.36 μs  )
    lazy-aeson/60MB        mean 248.6 ms  ( +- 736.6 μs  )
    buffer-builder/1kB     mean 5.512 μs  ( +- 77.39 ns  )
    buffer-builder/6kB     mean 30.29 μs  ( +- 459.9 ns  )
    buffer-builder/60kB    mean 307.0 μs  ( +- 3.640 μs  )
    buffer-builder/600kB   mean 3.001 ms  ( +- 75.72 μs  )
    buffer-builder/6MB     mean 33.05 ms  ( +- 336.3 μs  )
    buffer-builder/60MB    mean 308.5 ms  ( +- 3.489 ms  )
Re:New JSON encoder for Haskell that is up to 3x faster than... by unhammer on Monday October 19, 2020 @08:20AM (#24825652)
Oh, I was thinking more of memory usage (there's a huge difference between plain aeson and buffer-builder there, with large files), but I guess I should just give it a go :-)
Re:New JSON encoder for Haskell that is up to 3x faster than... by nikita-volkov on Monday October 19, 2020 @08:30AM (#24825714)
It might be the case that your memory usage data on "aeson" is outdated. Prior to some later releases it was rendering in two passes: first into AST (the Value type) than from that into ByteString (Builder). It's likely that your extended memory usage was coming from that. Later they had the `Encoding` abstraction introduced to avoid that 2-pass problem. Both "jsonifier" and "buffer-builder" avoid that 2-pass problem by design.