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

20201117: progress on NCEP system clock-related CONDUIT latencies

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: 20201117: progress on NCEP system clock-related CONDUIT latencies
  • Date: Tue, 17 Nov 2020 09:06:58 -0700
Hi Pete and Daryl,

Unidata User Support received the following notice regarding CONDUIT
latencies this morning:

 From:    Dustin Sheffler - NOAA Federal <address@hidden>
 Date:    Tue, 17 Nov 2020 10:08:51 -0500
 Hello Unidata,

 At long last we were able to get movement on the issue causing the latency on
 the NCEP CONDUIT systems and we now have them connecting to our time sync
 servers properly. Can you confirm that you are no longer seeing latencies?
 Thank you

Latency plots for the UCAR/Unidata and UWisc/AOS machines that are
REQUESTing the CONDUIT feed show the desired drop in latencies from
over 700s to the "normal' 0-30s.

I sent Dustin Sheffler a reply to his note acknowledging the desired
latency drop.

Cheers,

Tom
--