[gdal-dev] 回复： gdal-dev Digest, Vol 138, Issue 50

[alexto1978]

hello, i want to unsubscribe the email, and i cannot unsubscribe by website,thanj you.


发送自我的三星设备

-------- 原始邮件 --------
发件人： gdal-dev-request at lists.osgeo.org 
日期: 2015-11-29  04:00  (GMT+08:00) 
收件人： gdal-dev at lists.osgeo.org 
主题： gdal-dev Digest, Vol 138, Issue 50 

Send gdal-dev mailing list submissions to
	gdal-dev at lists.osgeo.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.osgeo.org/mailman/listinfo/gdal-dev
or, via email, send a message with subject or body 'help' to
	gdal-dev-request at lists.osgeo.org

You can reach the person managing the list at
	gdal-dev-owner at lists.osgeo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gdal-dev digest..."


Today's Topics:

   1. Changing default value for GDAL_CACHEMAX ? (was Re: Slow
      warping) (Even Rouault)


----------------------------------------------------------------------

Message: 1
Date: Sat, 28 Nov 2015 16:13:55 +0100
From: Even Rouault <even.rouault at spatialys.com>
To: Ari Jolma <ari.jolma at gmail.com>
Cc: gdal-dev at lists.osgeo.org
Subject: [gdal-dev] Changing default value for GDAL_CACHEMAX ? (was
	Re: Slow	warping)
Message-ID: <201511281613.55336.even.rouault at spatialys.com>
Content-Type: Text/Plain;  charset="utf-8"

Le vendredi 27 novembre 2015 13:43:34, Ari Jolma a écrit :
> 27.11.2015, 14:10, Even Rouault kirjoitti:
> > Try setting GDAL_CACHEMAX to 150 (6048 * 4032 * 3 = 73 MB. and a x 2
> > security margin)
> 
> This reduces the time into 4 s.
> 
> Quite a bit reduction from several hours.
> 
> Maybe the default is too low? 150 MB does not seem much.

Setting the default is not obvious because it depends on use cases and 
hardware configurations. What if people run 100 gdal_translate in parallel ? 
(not very common use cases admidetely, and people can still override the 
default)

Perhaps rather than a fixed value, a percentage of the total RAM would be more 
appropriate (*). Let's say 5% ? 
2 GB (which is the max for a 32 bit process) -> 100 MB
4 GB -> 200 MB
16 GB -> 800 MB.

We could also accept a GDAL_CACHEMAX=X% syntax

Even

(*) the ECW SDK does that for its own purposes, with a 25% default AFAIR

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com


------------------------------

Subject: Digest Footer

_______________________________________________
gdal-dev mailing list
gdal-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

------------------------------

End of gdal-dev Digest, Vol 138, Issue 50
*****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20151129/99968e10/attachment.html>