Re: [gdal-dev] GDALRasterBand::RasterIO and FlushCache

2013-06-01 Thread David Strip
On 5/31/2013 5:38 PM, Frank Warmerdam wrote: Note that the image cache will start discarding blocks on it's own when it is full. I think the default cache is about 64MB.I don't think that flushing the cache should be part of normal applications operations, though if you are very tight on m

Re: [gdal-dev] GDALRasterBand::RasterIO and FlushCache

2013-05-31 Thread Frank Warmerdam
David, I see I misunderstood about the free and it is already documented. So I think the docs are good now and that most users should never even need to think about the caching aspect. Best regards, Frank On Fri, May 31, 2013 at 4:38 PM, Frank Warmerdam wrote: > David, > > Note that the image

Re: [gdal-dev] GDALRasterBand::RasterIO and FlushCache

2013-05-31 Thread Frank Warmerdam
David, Note that the image cache will start discarding blocks on it's own when it is full. I think the default cache is about 64MB.I don't think that flushing the cache should be part of normal applications operations, though if you are very tight on memory you might want to alter the default

[gdal-dev] GDALRasterBand::RasterIO and FlushCache

2013-05-31 Thread David Strip
I'm reading a fairly large (at least to me) geotif (about 2GB) a line at a time. I noticed that memory usage increases as I read the image. It appears that what's going on is that the driver hangs onto these lines of the image, even though I'm providing the same buffer fo