Måns Rullgård wrote:
Mandeep Kumarmandeep.kumar@linaro.org writes:
Vladimir Pantelicvladoman@gmail.com writes:
Either I am doing something wrong or this libjpeg-turbo is not so turbo.
Libjpeg (turbo or regular) is full of inefficiencies. I guess they all add up.
My numbers should only be used for relative comparison purpose as djpeg decoding time that I sent also include time to read input file from filessystem. Actual decoding speed may be higher when special modification are done in djpeg application to read input from memory.
I doubt reading from a cached file can account for that much time. Besides, I presume Vladimir was reading his file from somewhere too.
my times have been measured around the libavcodec decode() call and include colorspace conversion to YUYV interleaved. I realize that libjpeg might have an additional YUV to RGB step that I did not do since my display is YUV capable.
However, no matter how slow libjpeg is, that's what lots of apps use, and thus improving it should be beneficial to them insofar jpeg decoding is a bottleneck.
sure, I did not mean for you to stop working on it :)