Dear all,
Is there a way to
speed up the response in an .esriAscii request. The speed
difference between a .nc and .esriAscii output format is huge. I
have an example dataset where the ascii output is taking ~30
minutes before the download starts, where the .nc request is
starting after ~6 seconds...
Source file is a .nc file (~2.5Gb) - 5 parameters. The request
is 1 parameter full BBOX....
Any ideas why this takes to long?
All help is appreciated.
Best regards,
Fred.
|
Dear Roy,
I can reproduce this
both on a 2.18 and 2.22 instance. I think you can reproduce
this on every ERDDAP instance actually, eg: nc output takes some
time as well, but esriAscii takes significant more time (didn't
wait to see the result, but clearly a lot longer - it might even
throw a proxy error/timeout)
https://coastwatch.pfeg.noaa.gov/erddap/griddap/nceiPH53sstd1day.esriAscii?sea_surface_temperature%5B(2023-03-31T12:00:00Z):1:(2023-03-31T12:00:00Z)%5D%5B(89.979):1:(-89.979)%5D%5B(-179.979):1:(179.979)%5D
vs
https://coastwatch.pfeg.noaa.gov/erddap/griddap/nceiPH53sstd1day.nc?sea_surface_temperature%5B(2023-03-31T12:00:00Z):1:(2023-03-31T12:00:00Z)%5D%5B(89.979):1:(-89.979)%5D%5B(-179.979):1:(179.979)%5D
Best regards and
thanks!
Fred.
Hi Roy, all,
I forgot to mention I could not see any related errors in the
logs.
Best regards,
Fred.
To view this discussion on the web, visit https://groups.google.com/d/msgid/erddap/ce9794c3-07b3-4e9b-6a14-5e7e62eabe3b%40vliz.be.
To view this discussion on the web, visit https://groups.google.com/d/msgid/erddap/4E312DD7-5699-493D-B7E8-6174EAF3C58A%40noaa.gov.