pixz VS libvips

That's really confusing since `pixz` exists and its "pixie" pronunciation actually works

https://github.com/vasi/pixz

pixz (https://github.com/vasi/pixz) is a nice parallel xz that additionally creates an index of tar files so you can decompress individual files. I wonder if dpkg could be extended to do something similar.

There's pixz, which indexes the tarball, allowing listing/extracting individual paths without decompressing the whole thing.

Also relevant is pixz [1] which can do parallel LZMA/XZ decompression as well as tar file indexing.

[1] https://github.com/vasi/pixz

Yes, it's as easy as installing pixz with symlinks pointing to xz (I think Debian even does this automatically as part of its post-installation scripts).

pixz - Parallel, indexed xz compressor. BSD-2-Clause

Not quite what you're asking, but if you're a 7-Zip fan and on Linux, you might be interested in pixz.

Read through the comments and was surprised no one mentioned libvips - https://github.com/libvips/libvips. At my current small company we were trying to allow image uploads and started with imagemagick but certain images took too long to process and we were looking for faster alternatives. It's a great tool with minimum overhead. For video thumbnails, we use ffmpeg which is really heavy. We off-load video thumbnail generation to a queue. We've had great luck with these tools.

After some research, I found libvips, a demand-driven, horizontally threaded image processing library. It is designed to run quickly while using as little as memory as possible.

Sharp is a fast and efficient image optimization Node.js module that makes use of the native libvips library.

h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.

if you're using linux (which it doesn't seem so) there's also vispdisp https://github.com/jcupitt/vipsdisp which is based on https://github.com/libvips/libvips which will likely take over how images are decoded in the future for everything, at least methodology wise.

The magic happens by way of a library called Libvips, which contains an ultra-high-speed low-memory image resizer.

imagor uses one of the most efficient image processing library libvips. It is typically 4-8x faster than using the quickest ImageMagick and GraphicsMagick settings.

Try the solutions here: https://github.com/libvips/libvips/issues/2479

in that case maybe take a look at https://github.com/libvips/libvips