Opened 18 years ago
Last modified 10 years ago
#1231 closed defect
Conversion from GeoJP2 to GeoTIF with JP2KAK Kakadu exceptionally slow — at Version 1
| Reported by: | Owned by: | warmerdam | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | GDAL_Raster | Version: | unspecified |
| Severity: | normal | Keywords: | jp2kak |
| Cc: | Mateusz Łoskot |
Description (last modified by )
Conversion from GeoJP2 to GeoTIF with JP2KAK Kakadu based JP2 driver exceptionally slow
A series of tests show that GDAL 1.3.2.0, released 2006/05/02 is exceptionally slow reading in a GeoJP2 and then writing out a GeoTIF, but only when using the JP2KAK Kakadu based driver.
Doing a conversion from GeoJP2 to GeoTIF with Kakadu directly using kdu_expand -i in.jp2 -o out.tif is 8 times faster than calling upon the GDAL JP2KAK Kakadu driver to do the same conversion.
Doing a conversion from GeoJP2 to GeoTIF using the GDAL JPEG2000 JasPer driver, which does use not hardware acceleration, is inexplicably twice as fast as asking the GDAL JP2KAK Kakadu driver, which does use AltiVec and SSE hardware acceleration, to do the same conversion. This is illogical.
Change History (1)
comment:1 by , 17 years ago
| Description: | modified (diff) |
|---|---|
| Priority: | high → normal |
| Severity: | major → normal |
Greg,
Could you test again with the trunk version of GDAL (or a daily snapshot of trunk).
Some substantial rewriting of the JP2KAK driver was done in an effort to optimize several cases.