[gdal-dev] Memory increase in postgis raster driver
even.rouault at spatialys.com
Wed Jul 20 05:37:44 PDT 2016
Le mercredi 20 juillet 2016 12:12:59, jramm a écrit :
> I am seeing a continuous, linear memory increase when reading sequential
> windows of a large postgis dataset. This is the same regardless of my
> GDAL_CACHEMAX settings
> If I run he same code on an equivalent GTiff dataset, I do not see the same
> increase in memory.
> I can see that the postgis dataset RasterIO implementation calls CacheTile
> for each tile it reads, which I think uses the GDAL caching mechanism - is
> it possible that, since each tile will be *new* (due to the sequential read
> over the dataset), it is somehow cached outside of the gdal cache/ignoring
> the CACHEMAX setting?
It should remain in the blocks managed by the global raster block cache.
Playing with GDAL_CACHEMAX when doing gdalinfo -checksum, I see it is honoured
(the top memory consumption of the process lowers when GDAL_CACHEMAX lowers).
valgrind does not show memleaks either.
> I'm just stabbing in the dark here as I can't really find a reason for it
> View this message in context:
> er-tp5277284.html Sent from the GDAL - Dev mailing list archive at
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
Spatialys - Geospatial professional services
More information about the gdal-dev