On vendredi 3 janvier 2020 16:03:47 CET Jeff McKenna wrote:
> On 2020-01-03 3:52 PM, Even Rouault wrote:
> > Do you build netCDF with a custom value of the CHUNK_CACHE_SIZE /
> > chunk-cache- size setting ?
> >
> > With the default (4 MB), runtime on my machine is about 7 minutes. But if
> > I
> >
But I do use
-DCHUNK_CACHE_SIZE=67108864 ^
-DDEFAULT_CHUNK_SIZE=67108864
And get ~6 sec with a GMT release build (before it was a debug build) but still
~27 sec with gdalinfo. All VS2019 builds
-Original Message-
From: gdal-dev On Behalf Of Jeff McKenna
On 2020-01-03 3:52 PM, Even Rouault wrote:
Do you build netCDF with a custom value of the CHUNK_CACHE_SIZE / chunk-cache-
size setting ?
With the default (4 MB), runtime on my machine is about 7 minutes. But if I
use --with-chunk-cache-size=67108864 as in
https://trac.osgeo.org/gdal/ticket/5291
On vendredi 3 janvier 2020 14:02:18 CET Jeff McKenna wrote:
> Hi Joaquim,
>
> I have tested your file on Windows 10 here, with the command:
>
> gdalinfo grav_29_img.nc -mm
>
> which takes about 5 seconds to execute fully. I am using MS4W 4.0.2
> (GDAL 2.4.3 , NetCDF 4.7.3 )
Jeff,
Do you b
Nope, rebuilt netCDF but same timings.
-Original Message-
From: gdal-dev On Behalf Of Joaquim Manuel
Freire Luís
Sent: Friday, January 3, 2020 6:26 PM
To: Jeff McKenna ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Slow GDALComputeRasterMinMax on nc grids
Hi Jeff,
Thanks for testi
Hi Jeff,
Thanks for testing this. Sure it's useful. It also reminded me that I have a
OSGeo4W with GDAL 2.4.1 but don't know which netCDF version, and using it took
... over 6 minutes.
My Windows netCDF lib is a bit old by now (I build it from source). It might be
it.
Hi Joaquim,
I have test
Hi Joaquim,
I have tested your file on Windows 10 here, with the command:
gdalinfo grav_29_img.nc -mm
which takes about 5 seconds to execute fully. I am using MS4W 4.0.2
(GDAL 2.4.3 , NetCDF 4.7.3 )
I haven't tested using your wrappers though, so imagine that my feedback
is not very use
Hi Even,
New Year, new mysteries. I'm having quite strange slow times in computing the
min/max of netCDF files.
In GMT we can read files via GDAL by appending =gd to the file name. So both of
these do a similar job
grdinfo grav_29_img.nc=gd
and
gdalinfo grav_29_img.nc -mm
and it takes around 2
