[gdal-dev] RE: Memory Error in _gdal.Band_ReadRaster(*args, **kwargs)

Paul Meems bontepaarden at gmail.com
Sun Aug 16 16:00:46 EDT 2009

Thanks Greg for your help about speeding things up.
But speed is the least of my problems.
I wouldn't mind waiting 72 hours if it gets the job done.
But even with this statement:
gdal_retile --config GDAL_CACHEMAX 4000-v -s_srs EPSG:28992 -of ECW -ps
17335 16000 -targetDir tiles large.ecw

I get the Memory error.

Do you also have any suggestion on that. Would be very much appreciated.


2009/8/14 Greg Coats <gregcoats at mac.com>

> It is my understanding that the default is
> gdal_translate --config GDAL_CACHEMAX 40 ...
> which equates to 40 MB of memory.
> If you want to allow gdal_translate to use say 2 GB of memory for
> gdal_translate --config GDAL_CACHEMAX 2000 ...
> In my experience, increasing GDAL_CACHEMAX substantially speeds up
> gdal_translate processing.
> Greg
> On Aug 14, 2009, at 4:08 PM, Paul Meems wrote:
>  I also noticed both gdal_translate and gdal_retile not use the full
>> potential of my hardware. I'm running Vista 64Bit on a AMD3 2.6Ghz quadcore
>> with 8GB RAM and only 2-2.5GB RAM was used by gdal_translate, leaving more
>> than 5 GB free and only 35-55% of my CPU was used. Do I need to set some
>> settings to speed things up?
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20090816/53ab48ec/attachment.html

More information about the gdal-dev mailing list