Re: [conduit] Large CONDUIT latencies to UW-Madison idd.aos.wisc.edu starting the last day or two.

  • To: "'Carissa Klemmer - NOAA Federal'" <carissa.l.klemmer@xxxxxxxx>
  • Subject: Re: [conduit] Large CONDUIT latencies to UW-Madison idd.aos.wisc.edu starting the last day or two.
  • From: "Patrick L. Francis" <wxprofessor@xxxxxxxxx>
  • Date: Mon, 22 Feb 2016 10:37:18 -0500
I canât compare from Colorado, but as a comparison it takes 2-4 seconds to 
download 4knam conus nest from my amazon ec2 box in Virginia.. Iâm setting up a 
push / pull there for GFS later today when Iâm back in the office and can 
compare that if you like :)

 

Sent from my Iphone 6s

 

 

 

From: Carissa Klemmer - NOAA Federal [mailto:carissa.l.klemmer@xxxxxxxx] 
Sent: Monday, February 22, 2016 9:51 AM
To: Patrick L. Francis <wxprofessor@xxxxxxxxx>
Cc: Pete Pokrandt <poker@xxxxxxxxxxxx>; Arthur A Person <aap1@xxxxxxx>; 
_NCEP.List.pmb-dataflow <ncep.list.pmb-dataflow@xxxxxxxx>; Bentley, Alicia M 
<ambentley@xxxxxxxxxx>; Michael Schmidt <mschmidt@xxxxxxxx>; Daes Support 
<daessupport@xxxxxxxxxx>; support-conduit@xxxxxxxxxxxxxxxx 
<conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] Large CONDUIT latencies to UW-Madison idd.aos.wisc.edu 
starting the last day or two.

 

Patrick,

So from the looks of your screen grab that is 7 minutes to download the 0.25 
GFS from our FTP server. Do you have ideas of how slow that is compared to 
normal from Colorado? I will be passing this information on to our IT folks.




Carissa Klemmer 
NCEP Central Operations 
Dataflow Team Lead
301-683-3835

 

On Mon, Feb 22, 2016 at 8:52 AM, Patrick L. Francis <wxprofessor@xxxxxxxxx 
<mailto:wxprofessor@xxxxxxxxx> > wrote:

 

All,

Something bigger than just CONDUIT users occurred on the 19th. We had numerous 
users of other servers complain of similar drops in transfer rates. A few of 
them were also able to move downloads to a new location where speeds were 
normal. We believe that this issue was outside of NCEP due to that reasoning. 
Having said that though, is anyone still seeing abnormal rates? 

 

 

Hi Carissa :)

 

>From our Amazon location in VA, everything is fine as it was on Fridayâ From 
>our colo facility, packet loss is still shown via 140.90.111.36, which is the 
>hop from gigapop to ncep.. here is an MTR showing the packet loss:

 

http://drmalachi.org/files/ncep/he-ncep.2016.02.22.jpg

 

Notice that since our colo is directly on the Hurricane Electric backbone, 
there are only a few hops to get to the ncep server, and pings only jump once 
they reach gigapop.

 

Here is a screen cap of current download speeds for 0.25deg gfs from the ncep 
server to our colo:

 

http://drmalachi.org/files/ncep/he-ncep.wget.2016.02.22.jpg

 

In order to ensure proper delivery, we have setup a push / pull from our amazon 
box to the colo, but most people probably wonât have that flexibility.. The 
issue appears to potentially be related to packetfiltering and / or redirection 
/ funneling via certain routes, but thatâs just a guess :)

 

Happy Monday :)

 

Cheers,

 

--patrick

 

 

 

 

-------------------------------------------------------

Patrick L. Francis

Vice President of Research & Development

 

Aeris Weather

 

 <http://aerisweather.com/> http://aerisweather.com/

 <http://modelweather.com/> http://modelweather.com/

 

 <http://facebook.com/wxprofessor/> http://facebook.com/wxprofessor/

 

--------------------------------------------------------