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

• To: Pete Pokrandt <poker@xxxxxxxxxxxx>
• Subject: Re: [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
• From: Anne Myckow - NOAA Federal <anne.myckow@xxxxxxxx>
• Date: Mon, 30 Aug 2021 17:24:15 -0400

Pete,

Random aside, can you please update your doco to say that Dataflow's email
list is now nco.dataflow@xxxxxxxx ? I'm CC'ing it here. That other email
address is going to get turned off within the next year.

Thanks,
Anne

On Wed, Aug 18, 2021 at 4:02 PM Pete Pokrandt <poker@xxxxxxxxxxxx> wrote:

> 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
>
>
>
>
>
> <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>
> -----
> Pete Pokrandt - Systems Programmer
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086  - poker@xxxxxxxxxxxx
>


-- 
Anne Myckow
Dataflow Team Lead
NWS/NCEP/NCO

• Follow-Ups:
  • Re: [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
    • From: Jesse Marks - NOAA Affiliate

• References:
  • [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
    • From: Pete Pokrandt