Community
Participate
Working Groups
jpeg too long for decoddecoder needs optimization; it is talking ing big images. Moreover imagedata is taking too much memory, + renderer makes the whole system lacking in response. pictures will be uploaded tonight at http://www.picsmart.com/swt-test-images/
opps something went wrong with my fingers and it was submitted with mangled text. here goes again jpeg decoder is taking too long for big images and requires optimization. Moreover imagedata is taking too much memory, + renderer makes the whole system lacking in response. There are two paths for this. existing java code optimization or by using some optimized native libraries. I would suggest to go for native as for jpeg and tiffs specially when they are big, byte code often happen to lack a lot behind native code.
Just so you know, we benched GIF image decoding in Java versus the same code written as a C native and found the C code to be only about 50% faster (i.e. 90 seconds for Java code, 60 seconds for C code in the benchmark we were running). This is significant, but not enough to solve most of the real-world problems. In any case, I agree that improving our image decoding performance would be a good thing. Given the above numbers, I think the problem is more complex than simply re-writing the code in C. Unfortunately, we aren't going to get to this in the R2.0 time frame. Anyone who wants to submit a proposal for improving image processing is welcome to. Ideally, this should include scenarios and benchmarks of specific problem areas. Even better would be to include a working implementation on all the platforms.
Moving from Later.
*** This bug has been marked as a duplicate of 24451 ***
