The compressing speed of libjpeg-turbo has no difference with libjpeg in my program

Question

My program runs on the android device, and the device is ARM system with NEON supported.

At first I used libjpeg to compress the RGB image(800*480) to jpeg. The speed was about 70ms for per image, but it was too slow for me. Later I found the libjpeg-turbo, seems it can improve the compressing speed with the NEON in ARM.

But after compiling and testing, I found their compressing speed almost the same. And the change of the quality and flag passed to tjCompress2 also took no effect. I have no idea whether something is wrong or something is missing in my program. Codes below :

tjhandle _jpegCompressor = tjInitCompress();

tjCompress2(_jpegCompressor, (unsigned char*)in, PARAM_WIDTH,
            PARAM_WIDTH*PERSIZE, PARAM_HEIGHT, PERSIZE,
            (unsigned char**)&out, (long unsigned int*)outlen, TJSAMP_444, 100,
            TJFLAG_FASTDCT);

tjDestroy(_jpegCompressor);

The jpeg buffer(out) is allocated and freed by myself.

The version of libjpeg-turbo I use is 1.4.2

My question is compared with libjpeg, the compressing speed of libjpeg-turbo has no any improvement. I want to check out whether my program has any mistake. — gold_luck, Apr 14 '16 at 01:26

score 1 · Answer 1 · answered Oct 13 '22 at 19:45

Many of the SIMD acceleration for libjpeg-turbo was only added in 2.1 (currently newest). On my MacBook M1 (ARM with Neon), libjpeg-turbo 2.1.0 is significantly faster both in compression and decompression than libjpeg 9e.

On libjpeg-turbo official site, you can find a table of SIMD coverage for components of JPEG compression and various architecture and in which version the accelerated code was added.

Based on experiment I carried out recently, the outputs of compression and decompression using libjpeg-turbo are identical backwards all the way to libjpeg 6b. Good job, libjpeg-turbo developers!

score 0 · Answer 2 · answered Aug 15 '16 at 22:09

As far as I know libjpeg-turbo has SIMD, SSE2, MMX instructions for x86 processor. I've looked at some of the assembly code and I didn't see any code for other types of CPU architectures.

I'm surprised it even worked. I think that it (the library) preserves the original code, that would explain why it was able to even run.

If you're looking for optimizations, you may want to look at optimizations you can do with the libjpeg itself. There are several documentation files, one specifically has instructions for optimizing on the ARM processor. You can also tweak the memory manager. You'll find a lot more information there, than what I can type here.

The compressing speed of libjpeg-turbo has no difference with libjpeg in my program

2 Answers2