Re: [gdal-dev] RFC 26: GDAL Block Cache Improvements

2009-12-07 Thread Even Rouault
Tamas, I agree with Frank's comments. The few remaining traces of subblocking mechanism should be removed : the bSubBlockingActive, nSubBlocksPerRow, nSubBlocksPerColumn members of GDALRasterBand and all associated code. I've an few additional comments on the patch : * The CACHE_SIZE_MAX =

Re: [gdal-dev] RFC 26: GDAL Block Cache Improvements

2009-12-06 Thread Frank Warmerdam
Tamas Szekeres wrote: I'm about to handle issue #1 by introducing RFC26 which would establish a hastable based caching solution in parallel to the current array based block cache implementation. As this change would affect the gdal core it seems reasonable to come up with a new RFC here and ope

[gdal-dev] RFC 26: GDAL Block Cache Improvements

2009-12-06 Thread Tamas Szekeres
Devs, I'm quite involved in fixing the problems have already been raised in http://n2.nabble.com/Problems-with-large-raster-sizes-WMS-TMS-td3996139.html Those issues are mostly related to the following issues: 1. The current GDAL block cache implementation may result in out of memory errors with