[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Top level CONDUIT relay

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: Top level CONDUIT relay
  • Date: Tue, 19 Jun 2007 12:37:23 -0600
Chi,

While the data feed from ldm1.ncep.noaa.gov is much better than when
pointing to ncepldm.woc.noaa.gov, there still appears to be significant
latency issues.
However, the constant disconnect and reconnect to ncepldm (if it was
rebooting
as Justin pointed out) was much worse.

I saw an initial return to what appeared to be normal flow for about 1
hour when feeding from ldm1.woc.noaa.gov, but since then have seen a
return of latency:

http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc_long?CONDUIT
+daffy.unidata.ucar.edu

I think an issue still exists.

Steve Chiswell
Unidata User Support

On Tue, 2007-06-19 at 13:50 -0400, Chi.Y.Kang wrote:
> Steve Chiswell wrote:
> > Pete and David,
> >
> > I changed the CONDUIT request lines at NSF and Unidata to request data
> > from ldm1.woc.noaa.gov rather than ncepldm.woc.noaa.gov after seeing
> > lots of
> > disconnect/reconnects to the ncepldm virtual name.
> >
> > The LDM appears to have caught up here as an interim solution.
> >
> > Still don't know the cause of the problem.
> >
> > Steve
> >   
> 
> I know the NCEP was stop and starting the LDM service on the ldm2 box
> where the VIp address is pointed to at this time.  how is the current
> connection to LDM1?  is the speed of the conduit feed acceptable?
> 
> 
> 
-- 
Steve Chiswell <address@hidden>
Unidata