|The architecture of PerlMagick|
Steven comments on the slowness of PerlMagick in the EXIF tag extraction case. I'm pretty sure that it's not forking a process though -- ImageMagick is now a set of libraries which are wrapped to make the command line utilities we all know and love, as well as PerlMagick. So, I don't think a fork is involved.
I think what is happening here is that ImageMagick is suffering from it's own generic (and therefore very powerful nature). In return for being able to do heaps of things with heaps of image formats, you get a block of code which simply as efficient as possible in all cases. I haven't done a code audit to determine if this is the case in this specific incident however.
So, I think PerlMagick is innocent here.
Tags for this post: imagemagick perlmagick image jpeg exif perl cgi
Related posts: ImageMagick slowness extracting EXIF information from JPEG files; The JPEG still picture compression standard; die() in a CGI; MacOS' RSS screen saver really unreliable?; Openstack compute node cleanup; Old ImageMagick packages in Debian and Ubuntu
posted at: 05:24 | path: /imagemagick | permanent link to this entry