3 ms·
Seems like imagemagick was coredumping and my measurement wasn't correct. So I raised imagemagick memory limits and I made sure both were using the same jpeg qu
by tecleandor 4y ago
Seems like imagemagick was coredumping and my measurement wasn't correct. So I raised imagemagick memory limits and I made sure both were using the same jpeg quality and downsampling filter and:
ImageMagick
time convert original.jpg -filter Lanczos -set option:filter:lobes 3 -resize 50% -quality 75% im.jpg
91.43s user 3.65s system 424% cpu 22.396 total
avg shared (code): 0 KB
avg unshared (data/stack): 0 KB
total (sum): 0 KB
max memory: 10553 MB
page faults from disk: 0
other page faults: 2993653
vips
time vips resize original.jpg "vips.jpg[Q=75]" 0.5 --kernel lanczos3
13.00s user 0.15s system 194% cpu 6.771 total
avg shared (code): 0 KB
avg unshared (data/stack): 0 KB
total (sum): 0 KB
max memory: 255 MB
page faults from disk: 11
other page faults: 60951
So Imagemagick does: 40x the memory, almost 4x the time, almost 9x the CPU time.
Versions and computer:
Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz (8 cores)
16GB RAM
Debian 11
Kernel 5.18.8-xanmod1-x64v2 (software not rebuilt for x64v2 instructions)
ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
vips-8.12.2-Mon Feb 28 21:28:00 UTC 2022
Options for zsh time:
TIMEFMT='%U user %S system %P cpu %*E total'$'\n'\
'avg shared (code): %X KB'$'\n'\
'avg unshared (data/stack): %D KB'$'\n'\
'total (sum): %K KB'$'\n'\
'max memory: %M 'MB''$'\n'\
'page faults from disk: %F'$'\n'\
'other page faults: %R'