[gdal-dev] Re: GDAL_retile slowdown at next level

christian.mueller at nvoe.at christian.mueller at nvoe.at
Tue May 11 08:39:47 EDT 2010

Please keep me informed, perhaps we can do an improvement by adding a  
command line argument for the cache size.

Quoting acangi <aca at ngi.be>:

> Thanks for the quick reply. I think it makes sense.
> First I'll try to move all data to a computing machine with a big hard disk,
> then if it's still slow, I'll try to increase self.cacheSize as you write.
> As gdal_retile.py isn't computing the empty tiles, I guess I can use :
> ( pixel width of the widest row in the previous level / tile width ) * 3  +
> 8
> because my widest row is still smaller than the width of the global extent.
> The widest row is 234000 pixels at level 1, so cacheSize would be 1380.
> Average size of a tile is 125 KB, thus my cache would be 170 MB, which
> shouldn't be a problem.
> Alain
> --
> View this message in context:   
> http://osgeo-org.1803224.n2.nabble.com/GDAL-retile-slowdown-at-next-level-tp5034870p5035428.html
> Sent from the GDAL - Dev mailing list archive at Nabble.com.
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev

This message was sent using IMP, the Internet Messaging Program.

More information about the gdal-dev mailing list