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.
Hi Art, re: > I'm looking at the latency graph > (www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.unidata.ucar.edu) > and seeing large latencies on some of the feeds... should I be concerned > about this? The latencies being shown for CONDUIT data coming from emo.unidata.ucar.edu to idd.unidata.ucar.edu went south: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.unidata.ucar.edu The portion of CONDUIT data that is showing high latencies is, however, small: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?CONDUIT+idd.unidata.ucar.edu My first guess is that the products with very high latencies are ones that are being received a second time, after the initially received ones have been scoured out of the queue on the receiving machine. > It seems to be translating into latencies downstream on our relay. Yes, but are the products being received with high latencies "second trip" ones? We will investigate to find out what is going on... Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: HNU-894965 Department: Support CONDUIT Priority: Normal Status: Closed