From 847fd641c051ee7ddc03ef77c01fe8f3d75e4baf Mon Sep 17 00:00:00 2001 From: Nigel Tao Date: Tue, 4 Jul 2017 09:41:05 +1000 Subject: [PATCH] Add more README.md benchmark detail. --- README.md | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 74b7fbec..ce21525b 100644 --- a/README.md +++ b/README.md @@ -641,14 +641,18 @@ TODO: also trawl through Go's bug tracker for "this image failed to load". ## Benchmarks -Preliminary `puffs bench` numbers for the GIF codec are below. "Mimic" tests -check that Puffs' output mimics exactly other libraries' output (i.e. giflib -for GIF, libpng for PNG, etc.). "Mimic" benchmarks are the numbers for those -other libraries, measured here on Ubunty 14.04 LTS "Trusty". +*Preliminary* `puffs bench` throughput numbers for the GIF codec are below. +Higher is better. -The 1k, 10k, etc. numbers are approximately how many pixels there are in the -decoded image. For example, the `test/testdata/harvesters.*` images are 1165 × -859, which is approximately 1000k pixels. +"Mimic" tests check that Puffs' output mimics exactly other libraries' output +(i.e. giflib for GIF, libpng for PNG, etc.). "Mimic" benchmarks are the numbers +for those other libraries, as shipped with the OS, measured here on Ubunty +14.04 LTS "Trusty". + +The 1k, 10k, etc. numbers are approximately how many bytes of pixel data there +is in the decoded image. For example, the `test/testdata/harvesters.*` images +are 1165 × 859 (approximately 1000k pixels) and a GIF image (a paletted image) +is 1 byte per pixel. name speed gif_puffs_decode_1k/clang 389MB/s ± 2% @@ -671,6 +675,11 @@ decoded image. For example, the `test/testdata/harvesters.*` images are 1165 × gif_mimic_decode_100k/gcc 100MB/s ± 0% gif_mimic_decode_1000k/gcc 102MB/s ± 0% +The mimic numbers measure the pre-compiled library that shipped with the OS, so +it is unsurprising that they don't depend on the C compiler (clang or gcc) used +to run the test harness. + + ## Code Size TODO.