Opened 13 years ago
Closed 9 years ago
#3991 closed defect (invalid)
gdal 1.8.0 slow
Reported by: | noog | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | default | Version: | 1.8.0 |
Severity: | normal | Keywords: | |
Cc: |
Description (last modified by )
hello i upgraded my version of gdal from 1.7.3 to 1.8.0 but the new version is very slow this is the result
gdal 1.7.3
0.76 % 155 / 20412 --- lvl 17 : 0.02 % 5 / 20412 time : 3 s remain. 6mn 32s gdalwarp -s_srs EPSG:27561 -t_srs EPSG:4326 -of GTiff -dstalpha -r lanczos -ts 256 256 -te 7.646484375 48.425555463221 7.6492309570312 48.427378042075 "./ortho/ortho2007.ecw" "./tmp/5b00677a35a1f0070de56cd215e88eea/tile.tif"
gdal 1.8.0
0.74 % 151 / 20412 --- lvl 17 : 0 % 1 / 20412 time : 20 s remain. 44mn 44s gdalwarp -s_srs EPSG:27561 -t_srs EPSG:4326 -of GTiff -dstalpha -r lanczos -ts 256 256 -te 7.635498046875 48.425555463221 7.6382446289062 48.427378042075 "./ortho/ortho2007.ecw" "./tmp/7fd1a07d8c9fbeeb43edcab84b249362/tile.tif"
Change History (9)
comment:1 by , 13 years ago
Description: | modified (diff) |
---|
follow-up: 3 comment:2 by , 13 years ago
I'm not familiar with what you are using to time the operation. Is the summary that 1.7 was 6 minutes and 1.8 was 44 minutes?
comment:3 by , 13 years ago
Replying to warmerdam:
I'm not familiar with what you are using to time the operation. Is the summary that 1.7 was 6 minutes and 1.8 was 44 minutes?
yes that's it
comment:4 by , 13 years ago
ok this is a gdalinfo result
Driver: ECW/ERDAS Compressed Wavelets (SDK 3.x) Files: ortho/ortho2007.ecw Size is 157465, 193707 Coordinate System is: PROJCS["LM1FRE1D", GEOGCS["N.T.F", DATUM["NTFPARIS", SPHEROID["CLA80IGN",6378249.2,293.4660213]], PRIMEM["Greenwich",0], UNIT["degree",0.0174532925199433]], PROJECTION["Lambert_Conformal_Conic_1SP"], PARAMETER["latitude_of_origin",49.5], PARAMETER["central_meridian",2.337229166666664], PARAMETER["scale_factor",0.999877341], PARAMETER["false_easting",600000], PARAMETER["false_northing",200000], UNIT["Meter",1]] Origin = (987000.000000000000000,126500.000000000014552) Pixel Size = (0.160036579789666,-0.160036579789666) Corner Coordinates: Upper Left ( 987000.000, 126500.000) ( 7d36' 2.34"E, 48d43' 2.78"N) Lower Left ( 987000.000, 95499.794) ( 7d34'17.07"E, 48d26'21.63"N) Upper Right ( 1012200.160, 126500.000) ( 7d56'31.78"E, 48d42' 3.99"N) Lower Right ( 1012200.160, 95499.794) ( 7d54'39.73"E, 48d25'23.17"N) Center ( 999600.080, 110999.897) ( 7d45'22.68"E, 48d34'13.35"N) Band 1 Block=157465x1 Type=Byte, ColorInterp=Red Overviews: 78732x96853, 39366x48426, 19683x24213, 9841x12106, 4920x6053, 2460x3026, 1230x1513, 615x756, 307x378, 153x189 Band 2 Block=157465x1 Type=Byte, ColorInterp=Green Overviews: 78732x96853, 39366x48426, 19683x24213, 9841x12106, 4920x6053, 2460x3026, 1230x1513, 615x756, 307x378, 153x189 Band 3 Block=157465x1 Type=Byte, ColorInterp=Blue Overviews: 78732x96853, 39366x48426, 19683x24213, 9841x12106, 4920x6053, 2460x3026, 1230x1513, 615x756, 307x378, 153x189
how can i change my input file (ecw) in tiff first ? thks
follow-up: 6 comment:5 by , 13 years ago
Status: | new → assigned |
---|
Well, you could do:
gdal_translate ortho/ortho2007.ecw ortho2007.tif
However your file is very large so that might take a while and quite a bit of disk space.
comment:6 by , 13 years ago
Replying to warmerdam:
Well, you could do:
gdal_translate ortho/ortho2007.ecw ortho2007.tifHowever your file is very large so that might take a while and quite a bit of disk space.
ok i have this error is there a way to repair an ecw file ? i presume the file corrupted, but i can open it in qgis
gdal_translate ortho2007.ecw ortho2007.e ...10...20. ..ERROR 1: Could not perform Read/Write on file
comment:7 by , 13 years ago
Hello i took another ecw file then i translated it in ecw format but the result is very slow too
CONVERT: 0 0.77 % 157 / 20412 --- lvl 17 : 0.03 % 7 / 20412 time : 1mn 58s remain. 4h13 gdalwarp -s_srs EPSG:27561 -t_srs EPSG:4326 -of GTiff -dstalpha -r lanczos -ts 256 256 -te 7.6519775390625 48.425555463221 7.6547241210937 48.427378042075 "./ortho/cus16.tiff" "./tmp/9f10e4c871d586d9bd5dd19ad9e17b97/tile.tif"
comment:8 by , 13 years ago
sorry i translated it in
tiff
format with the command gdal_translate but the result is very slow too
comment:9 by , 9 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Sorry if someone feels it too strict to call this issue as invalid because GDAL 1.8.0 was obviously slower than GDAL 1.7.3 for this user. However, 1.8.0 was a long time ago and other users have not commented this ticket.
Unfortunately this isn't much information to go on.
One thing I'm suspecting is that the slowness might relate to use of the ecw file as input. The ECW driver has been updated substantially and in some access patterns it might be slower. Could you try translating your input file to TIFF first to see if the ECW driver is the culprit?
Depending on what we find out from that we will either need the input file, or perhaps a gdalinfo report on the input file so we can setup something similar.