Opened 18 years ago
Last modified 13 years ago
#1221 closed defect
Read JP2 with Jasper driver excrutiatingly slow — at Version 2
| Reported by: | Owned by: | dron | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | GDAL_Raster | Version: | unspecified |
| Severity: | normal | Keywords: | jpeg2000 jasper |
| Cc: | arturr, Mateusz Łoskot |
Description (last modified by )
Reading a JP2 with the JasPer driver is extremely slow. Wrting JP2 with JasPer works fine. A 5000x5000 pixel color JP2 (lossless) takes over 5 minutes to tick over the progress meter. As a comparison, reading the same JP2 with the MrSID JP2 driver takes 1.3 minutes for the full image. Outsides of GDAL, with the jasper program (same jasper libraries that GDAL uses), it takes 30 sec to read the full image. There is nothing in the console log to indicate a problem. It passes the gdalautotests, but those are small files so the speed problem is not noticable. GDAL 1.3.2
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Cc: | added |
|---|---|
| Description: | modified (diff) |
| Keywords: | jpeg2000 jasper added |
| Owner: | changed from to |
| Priority: | high → normal |
Andrey,
Any thoughts? I'm not clear on why geojasper would be any faster - perhaps arturr can expand on this.
Note:
See TracTickets
for help on using tickets.
can jasper be exchanged into geojasper(much faster and uses less memory)?