Opened 14 years ago
Closed 11 years ago
#3746 closed defect (invalid)
georaster-Poor performance on large dataset
Reported by: | ilucena | Owned by: | ilucena |
---|---|---|---|
Priority: | high | Milestone: | 1.8.1 |
Component: | GDAL_Raster | Version: | svn-trunk |
Severity: | normal | Keywords: | georaster |
Cc: | warmerdam |
Description
The poor performance on large dataset is mostly because it is creating a very large array of loblocator on the server side with all the RTD rows of the GeoRaster.
That affects the process of loading and extracting data but mostly significantly on visualization applications when it also has to deal with pyramids rows on the RDT.
Change History (2)
comment:1 by , 14 years ago
comment:2 by , 11 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Correction: "That *dos not* affects the process of loading and extracting data but mostly significantly on visualization applications when it also has to deal with pyramids rows on the RDT."
The very large array of loblocator has not been a problem for well tuned system.
There is an experimental version of the code that is on:
http://trac.osgeo.org/gdal/browser/sandbox/ilucena/georaster
That is what we are using for FOSS4G2010 benchmarking:
http://wiki.osgeo.org/wiki/Benchmarking_2010#MapServer
It passed the gdal_autotest successfully but it would need more testing before committing it to the trunk.