Jpegli doesn’t appear to use SIMD acceleration either, unless I’m missing something.
> On Apr 4, 2024, at 8:54 AM, DRC <d...@virtualgl.org> wrote: > > > https://opensource.googleblog.com/2024/04/introducing-jpegli-new-jpeg-coding-library.html > > I am out of the office right now and unable to evaluate this, but suffice it > to say that I doubt their claims of compression performance parity. Images > compressed with Jpegli should decompress as quickly as images compressed with > libjpeg-turbo, but there is additional compute complexity involved with > generating custom quantization tables. Thus, the compression should be slower > (although perhaps not as slow as mozjpeg.) -- You received this message because you are subscribed to the Google Groups "libjpeg-turbo User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to libjpeg-turbo-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/libjpeg-turbo-users/32CFEED4-D83D-4561-8638-23624458CD44%40virtualgl.org.
