[conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov

Dear Anne, Dustin and all,

Recently we have noticed fairly high latencies on the CONDUIT ldm data feed originating from the machine vm-lnx-conduit2.ncep.noaa.gov. The feed originating from vm-lnx-conduit1.ncep.noaa.gov does not have the high latencies. Unidata and other top level feeds are seeing similar high latencies from vm-lnx-conduit2.ncep.noaa.gov.

Here are some graphs showing the latencies that I'm seeing:

From https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd-agg.aos.wisc.edu - latencies for CONDUIT data arriving at our UW-Madison AOS ingest machine

From https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?conduit.unidata.ucar.edu (latencies at Unidata)

At least here at UW-Madison, these latencies are causing us to lose some data during the large GFS/GEFS periods.

Any idea what might be causing this?

Pete

-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - address@hidden

_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


conduit mailing list
address@hidden
For list information or to unsubscribe, visit: 
https://www.unidata.ucar.edu/mailing_lists/