Ognjen,
Thanks for pointing that out. Someone had already called my attention to
that thread, which is indeed the same issue I faced.
Jeremias suggested (private communication) a different approached, which
I tried, and consists in having an "alternative" optimizedWriteTo()
function to deal just with BGR images. It is very much like the original
one, except that the B and R bytes are permuted (so that we get RGB)
before performing the write call. That led to very good performance
gains when the CPU is underutilized, although the gains are less
impressive when the CPU saturates.
Luis
On 2/7/12 11:40 PM, Ognjen Blagojevic wrote:
Luis,
On 6.2.2012 13:11, Luis Bernardo wrote:
follows the writeRGBTo() path instead of the previous
optimizedWriteTo() path. The end result is a 40% performance impact
for the PNG file I have been testing with when going from jdk1.6_13 to
a more recent one, like jdk1.6_30.
Any ideas on how to recover the previous performance (i.e., use the
optimizedWriteTo() path)?
Take a look at this thread:
http://www.mail-archive.com/[email protected]/msg13492.html
And this issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=51149
I was able to recover performance by removing color profile
information from PNG.
-Ognjen
