|
Art,
I don't know if NCEP ever figured anything out, but I've been able to keep my latencies reasonable (300-600s max, mostly during the 12 UTC model suite) by splitting my CONDUIT request 10 ways, instead of the 5 that I had been doing, or in a single request. Maybe give that a try and see if it helps at all.
Pete
-- From: Person, Arthur A. <address@hidden>
Sent: Monday, March 11, 2019 3:45 PM To: Holly Uhlenhake - NOAA Federal; Pete Pokrandt Cc: address@hidden; address@hidden Subject: Re: [conduit] Large lags on CONDUIT feed - started a week or so ago Holly,
Was there any resolution to this on the NCEP end? I'm still seeing terrible delays (1000-4000 seconds) receiving data from conduit.ncep.noaa.gov. It would be helpful to know if things are resolved at NCEP's end so I know whether to look further down the line.
Thanks... Art
Arthur A. Person From: address@hidden <address@hidden> on behalf of Holly Uhlenhake - NOAA Federal <address@hidden>
Sent: Thursday, February 21, 2019 12:05 PM To: Pete Pokrandt Cc: address@hidden; address@hidden Subject: Re: [conduit] Large lags on CONDUIT feed - started a week or so ago Hi Pete,
We'll take a look and see if we can figure out what might be going on. We haven't done anything to try and address this yet, but based on your analysis I'm suspicious that it might be tied to a resource constraint on the VM or the blade it resides on.
Thanks,
Holly Uhlenhake
Acting Dataflow Team Lead
On Thu, Feb 21, 2019 at 11:32 AM Pete Pokrandt <address@hidden> wrote:
|
_______________________________________________ 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: http://www.unidata.ucar.edu/mailing_lists/