Carissa,
I based my 'no improvement' solely on the output of the traceroutes and mtr (which didn't really seem to change) and on the red line on that Unidata latency graph which had not changed.
I have since changed my CONDUIT requests to point to conduit.ncep.noaa.gov (first) and ncepldm4.woc.noaa.gov (second) and so far there seems to be a drastic improvement over what I was seeing last week. Looking at that same graph (time goes from left to right, so far left is about 3 days ago, right side is right now)
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.aos.wisc.edu
my latencies are now down around 60 seconds or so max, whereas last Friday they were over 3600s. The red line on that graph appears to be related to my path through idd.unidata.ucar.edu, (since it's not there now that I'm not currently pulling CONDUIT from idd.unidata.ucar.edu) though for reasons I don't fully understand it didn't seem to affect my data delivery. The low latencies of the blue and green line below were making up for it and data was coming in completely and timely.
I don't understand why last Friday when this started, and I had requests to both conduit.ncep.noaa.gov and ncepldm4.woc.noaa.gov, I was seeing huge latencies, but when I changed to request from idd.unidata.ucar.edu (which had the red big lag) and ncepldm4.ncep.noaa.gov the data came in completely. It's almost as if when I had conduit.ncep.noaa.gov and ncepldm4.woc.noaa.gov in there last week, the ldm was not using/finding the lower latency site. Very strange and I don't understand it.
But bottom line is my transfer rates from conduit.ncep.noaa.gov DO seem to have greatly improved.
Thanks all for the investigation and work on this Pete
From: Carissa Klemmer - NOAA Federal <address@hidden>
Sent: Thursday, February 25, 2016 11:50 AM To: Pete Pokrandt Cc: address@hidden; address@hidden; Gerry Creager - NOAA Affiliate Subject: Re: [conduit] Slower transfer rates from NCEP Pete,
Can you confirm that the slow downs to Boulder also started on Friday? And we'd appreciate testing conduit.ncep again. You are the first who has said they haven't seen an improvement. Before I
report this I'd like to be 100% sure that both Boulder and conduit.ncep (Maryland) are bad.
Carissa Klemmer
NCEP Central Operations Dataflow Team Lead 301-683-3835 On Thu, Feb 25, 2016 at 12:15 PM, Pete Pokrandt
<address@hidden> wrote:
|