[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #EDH-245819]: THREDDS OPeNDAP Performace

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.


  • Subject: [THREDDS #EDH-245819]: THREDDS OPeNDAP Performace
  • Date: Thu, 13 Apr 2017 11:24:59 -0600

Your observation is correct. We took the dap2 code from
OPeNDAP.org many years ago and have known about this dual
copy problem for a long time. Until recently, this has been only
a mild problem because very large data requests thru DAP2 were
uncommon.
It is unlikely that we will attempt to improve the code
because it would be a large undertaking and we do not wish
to devote the necessary the resources to do it.  
Instead, we have been focusing on the DAP4 protocol in Thredds version 5.
This was designed from the start to be single copy. It takes the data
directly from the underlying source and converts and transmits it only once.

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: EDH-245819
Department: Support THREDDS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.