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 John, re: > Our CONDUIT feed seems to be developing large latencies in the last > few days: > > http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+adiabat.rwic.und.edu > > I haven't changed the configuration and the machine looks fine. Any > ideas? I see that your CONDUIT latencies dropped immediately after you switched your upstream feed host from bigbird.tamu.edu to idd.unidata.ucar.edu. My impression, therefore, would be that the latencies you were seeing when feeding from bigbird were a result of either a problem on bigbird or in the network connection between adiabat and bigbird. A quick check of bigbird's latencies: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+bigbird.tamu.edu shows no problems, so I am left with the impression that there was some sort of a routing problem (or traffic limiting "packet shaping") between adibat and bigbird. 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: ZWV-440954 Department: Support CONDUIT Priority: Normal Status: Closed