mirror of
https://github.com/ddidderr/wuffs.git
synced 2026-11-17 16:32:11 +01:00
The benchmarks don't exercise the RGB code paths per se, but it does affect the numbers. Especially for gcc, this essentially undoes the performance impact of the previous (trivial) commit. This is all presumably another code alignment coincidence per https://news.ycombinator.com/item?id=23633583 name old speed new speed delta wuffs_jpeg_decode_19k_8bpp/clang11 376MB/s ± 0% 376MB/s ± 0% ~ (p=1.000 n=5+5) wuffs_jpeg_decode_30k_24bpp_progressive/clang11 338MB/s ± 0% 341MB/s ± 0% +0.98% (p=0.008 n=5+5) wuffs_jpeg_decode_30k_24bpp_sequential/clang11 1.01GB/s ± 0% 1.01GB/s ± 0% +0.35% (p=0.008 n=5+5) wuffs_jpeg_decode_77k_24bpp/clang11 841MB/s ± 0% 836MB/s ± 1% -0.65% (p=0.008 n=5+5) wuffs_jpeg_decode_552k_24bpp_420/clang11 913MB/s ± 0% 912MB/s ± 0% -0.18% (p=0.016 n=5+5) wuffs_jpeg_decode_552k_24bpp_444/clang11 1.11GB/s ± 0% 1.10GB/s ± 0% -0.34% (p=0.008 n=5+5) wuffs_jpeg_decode_4002k_24bpp/clang11 920MB/s ± 0% 916MB/s ± 0% -0.42% (p=0.008 n=5+5) wuffs_jpeg_decode_19k_8bpp/gcc10 349MB/s ± 0% 368MB/s ± 0% +5.60% (p=0.008 n=5+5) wuffs_jpeg_decode_30k_24bpp_progressive/gcc10 328MB/s ± 0% 279MB/s ± 0% -14.82% (p=0.008 n=5+5) wuffs_jpeg_decode_30k_24bpp_sequential/gcc10 925MB/s ± 0% 947MB/s ± 1% +2.33% (p=0.008 n=5+5) wuffs_jpeg_decode_77k_24bpp/gcc10 732MB/s ± 0% 770MB/s ± 0% +5.23% (p=0.008 n=5+5) wuffs_jpeg_decode_552k_24bpp_420/gcc10 798MB/s ± 0% 838MB/s ± 0% +4.99% (p=0.008 n=5+5) wuffs_jpeg_decode_552k_24bpp_444/gcc10 962MB/s ± 0% 996MB/s ± 0% +3.54% (p=0.008 n=5+5) wuffs_jpeg_decode_4002k_24bpp/gcc10 806MB/s ± 0% 847MB/s ± 0% +5.19% (p=0.008 n=5+5)
This directory contains third party test data, not checked into the repository directly for download size and copyright reasons.
It also contains derived summary data files (such as nia-checksums-of-*.txt)
which are checked into the repository, for regression testing.