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

[IDD #HNU-894965]: CONDUIT latency at idd.unidata.ucar.edu?

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: [IDD #HNU-894965]: CONDUIT latency at idd.unidata.ucar.edu?
  • Date: Wed, 21 Nov 2007 10:50:15 -0700
Art,

NCEP enabled a new LDM server which was supplying redundand source of data, so 
a few second
trip products were coming through. Dtaa wasn't being lost, but second trip 
products were showing
as high latency. I have restricted the source of data to avoid these repeat 
products for now.

Steve Chiswell
Unidata User Support



> Tom,
> 
> On Tue, 20 Nov 2007, Unidata CONDUIT Support wrote:
> 
> > Hi Art,
> >
> > re:
> >> I'm looking at the latency graph
> >> (www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.unidata.ucar.edu)
> >> and seeing large latencies on some of the feeds... should I be concerned
> >> about this?
> >
> > The latencies being shown for CONDUIT data coming from emo.unidata.ucar.edu
> > to idd.unidata.ucar.edu went south:
> >
> > http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.unidata.ucar.edu
> >
> > The portion of CONDUIT data that is showing high latencies is, however, 
> > small:
> >
> > http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?CONDUIT+idd.unidata.ucar.edu
> >
> > My first guess is that the products with very high latencies are ones that 
> > are being
> > received a second time, after the initially received ones have been scoured 
> > out of
> > the queue on the receiving machine.
> >
> >> It seems to be translating into latencies downstream on our relay.
> >
> > Yes, but are the products being received with high latencies "second trip" 
> > ones?
> > We will investigate to find out what is going on...
> 
> I dunno... the only reason I mentioned it was because on our volume graph
> for idd-ingest.meteo.psu.edu, most of the volume is green and on the
> latency graph, the high latencies are green.  Do those colors actually
> correlate?  I don't think we've actually noticed data loss (that I've
> noticed, at least).  It looks like the latencies flat-topped in a couple
> of places, so I'm guessing there was a little bit of data loss as
> latencies exceeded 3600 seconds...
> 
> Art
> 
> > Cheers,
> >
> > Tom
> > ****************************************************************************
> > Unidata User Support                                    UCAR Unidata Program
> > (303) 497-8642                                                 P.O. Box 3000
> > address@hidden                                   Boulder, CO 80307
> > ----------------------------------------------------------------------------
> > Unidata HomePage                       http://www.unidata.ucar.edu
> > ****************************************************************************
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: HNU-894965
> > Department: Support CONDUIT
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> Arthur A. Person
> Research Assistant, System Administrator
> Penn State Department of Meteorology
> email:  address@hidden, phone:  814-863-1563
> 
> 


Ticket Details
===================
Ticket ID: HNU-894965
Department: Support CONDUIT
Priority: Normal
Status: Closed