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

• To: "anne.myckow@xxxxxxxx" <anne.myckow@xxxxxxxx>, "dustin.sheffler@xxxxxxxx" <dustin.sheffler@xxxxxxxx>, "ncep.list.pmb-dataflow@xxxxxxxx" <ncep.list.pmb-dataflow@xxxxxxxx>
• Subject: [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
• From: Pete Pokrandt <poker@xxxxxxxxxxxx>
• Date: Wed, 18 Aug 2021 20:02:13 +0000
• Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=aos.wisc.edu; dmarc=pass action=none header.from=aos.wisc.edu; dkim=pass header.d=aos.wisc.edu; arc=none
• Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GVcjsIvjoJs80hVtP6n6MPCRmnxxogavq7rk4XdyMvY=; b=e7Cxl1C0Jyt4oeKHucc1r3EkRllo6aodPKkIA3jxFXAoKVe/jAx8tpWYz2gc9U2BE4CvSsP87DxvRqvpOwKLAzSXiz6sl189KlwMotc0ixFaaa4I5TPR99+IodIKEkP8OJo7EMvaM+jEPXwSpzzTYJhfP7YdHVgZUfA/JtH7YzsCgE0gvyxHHijoT0FfksDdFlYPJge0ToUxZrZ6uP43ZiKG4KxOdeA/LJV9gTFDvEWe3b4Os28qkfwfUwmlrj/QnICkM19a1If9yk0RcQ0O4TAfC8bVPBsE+m6mcnFlPwXeQGeWN+RnetdlPJy74aGdk3Xy+nGv4qHVL3FCU5i4fA==
• Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Qev23ylQ3U1+TN7a7zSIjeNL090e+Ax+suzwwFAPvxTvKyYdvyv8idBuv6NFXBn9HMfS/snXXl98nsor2p5MIIk7qhigPxW4iQfK5ZS+ABH435e1v3ZK2XeK6105WtesPjCnXS+MZDiAV60Zkjr7CcEd6WYA5aHjmKuTNe3K2wnbnjJu7VhogmES7QkMHR0QscEt8NG4splEWvusS7wFb/7tjDx8JIqVShkHuSfHiZjNxaPc8AtMKSRibNuIoHfmcYmp4bahdBdZLGgMkDrrkSmHmCf6yQ/b1d2O1vjLA1BLZYyWs8B+4mITnsrRqAbHUjJoCHAMFYuVE+AmnfqI4Q==

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

[cid:cb4fda71-be88-450e-bf39-4346eb77ba50]

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

[cid:50b9a476-503f-4e75-b22b-4bc99eff3cdc]

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

• Follow-Ups:
  • Re: [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
    • From: Anne Myckow - NOAA Federal
  • Re: [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
    • From: Pete Pokrandt