[Gdal-dev] Wanted: More speed to JPEG2000

Tom Lynch tflynch at gmail.com
Fri Nov 24 02:11:07 EST 2006

On 11/24/06, Rahkonen Jukka <Jukka.Rahkonen at mmmtike.fi> wrote:
> Hi,
> I have noticed that there is quite a big difference between using ECW and JPEG2000 format images through GDAL and MapServer path.  While I could get in a quite well controlled test some 120 images per minute ripped out from  ECW layer it was just 80 image per minute from JPEG2000 layer with JP2ECW driver and miserly 25 images/min with JP2KAK driver.
> I wonder if there is any chance to improve the JPEG2000 even close to ECW efficiency?  Slow results with JP2KAK driver is propably due to not so optimal implementation, but is there some explanation for the difference between ECW and JPEG2000 with the ER Mapper driver?

Hi Jukka,

The performance difference you observe between ECW and JPEG 2000 with
the JP2ECW driver is a consequence of the differences between the
formats and our implementations of their codecs.  We're actively
trying to improve performance on both sides of the equation but the
additional flexibility of JPEG 2000, and the computational cost of its
decoder do impose an additional overhead.  Further effort into JPEG
2000 decoder optimisation is producing diminishing returns as we

Also, if you're working on a platform other than Windows there are
still some hardware-based optimisations for JPEG 2000 (SSE stuff) that
don't make it into the build.

The default compression settings for the GDAL JP2ECW driver in the
absence of other options specified are those of the underlying ECW
JPEG 2000 SDK itself - RPCL progression order, no tiles, precinct size
determined as a function of dataset dimension.  These should be pretty
much optimal for GIS-interactive usage pattern of the data, so there
may not be much room for improvement here either.


Tom Lynch
ER Mapper

More information about the Gdal-dev mailing list