Slow opendap server

[Zachary Griffith]

This server is extremely slow (~15-30 s response times) – do you know why?  I have used it in the last couple months with no issues.

 

Thanks,

Zach


# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
# 
# We're sorry you had a problem using the server.
# Please use the space above to describe what you
# were trying to do and we will try to assist you.
# Thanks,
# OPeNDAP Support.
# 
# -- -- -- hyrax location info, please include -- -- --
# 
# ReqInfo.getRequestUrl(): https://ladsweb.modaps.eosdis.nasa.gov/opendap/hyrax/RemoteResources/laads/
# request_url: http://ladsweb.modaps.eosdis.nasa.gov/opendap/hyrax/RemoteResources/laads/
# protocol: HTTP/1.1
# server: ladsweb.modaps.eosdis.nasa.gov
# port: 80
# javax.servlet.forward.request_uri: null
# query_string: n/a
# status: 200
# 
# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

 

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

Zachary Griffith

Atmosphere SIPS and TROPICS DPC

University of Wisconsin - Madison

Space Science and Engineering Center

[Miguel Jimenez]

Hi Zach, 

Yeah - 15-30 sec per response could be due to a myriad of reasons. Assuming your workflow has not changed, and that this sub- performance is relatively recent, it could be an underlying issue within NASA’s system (sometimes there are issues with NASA’s CMR which the server in the background). 

That said, to better diagnose what is going on, or possible offer an improved approach, would you mind sharing a snippet of your workflow? A minimal reproducible example would be great!

Thanks

Miguel Jimenez-Urias, PhD
Computational Oceanographer | Sc. Community Director
OPeNDAP, Inc

https://www.linkedin.com/in/MiguelJimenezUrias/