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

[IDD #HOA-343163]: NEXRAD2 slowdown?

Hi John,

Thanks for all your help! Could you please perform a:

traceroute bigbird.tamu.edu

and a:

traceroute idd.unidata.ucar.edu

From:

adiabat.rwic.und.edu

and attach and return the output of the commands.

Thanks again,

> Ok, here's all the NEXRAD2 lines I have in my ldmd.conf file:
> 
> # request NEXRAD2 ".*" bigbird.tamu.edu
> request NEXRAD2 ".*" idd.unidata.ucar.edu
> 
> I've restarted ldm on adiabat at 2:04 pm CT.
> 
> On Mon, 27 Nov 2006, Unidata IDD Support wrote:
> 
> > Hi John,
> >
> > Just for clarification, please comment out the request to bigbird for 
> > NEXRAD2, this way we can see how the data via idd.unidata.ucar.edu is being 
> > delivered, if we just add idd.unidata.ucar.edu to the request line,  the 
> > LDM will grab data from whomever has it first, and this may nullify our 
> > "test" of getting data from idd.
> >
> > Thanks for helping,
> >
> > Jeff
> >
> >> Hi Tom.
> >>
> >> Yes, we'd be willing to do this.  My appologies for not replying
> >> to you sooner, I was on vacation over the Thanksgiving holiday and didn't
> >> see your email until today.
> >>
> >> =========================================================================
> >> John Nordlie   N0RNB            |     Regional Weather Information Center
> >> address@hidden            |              University of North Dakota
> >> http://blizzard.rwic.und.edu/~nordlie/
> >> =========================================================================
> >>
> >> On Wed, 22 Nov 2006, Unidata IDD Support wrote:
> >>
> >>> Hi John,
> >>>
> >>> re:
> >>>> Ok, I've switched the line to
> >>>>
> >>>> request NEXRAD2 ".*" bigbird.tamu.edu
> >>>
> >>> We were very concerned by the high latencies you were seeing when feeding
> >>> NEXRAD Level II data from our toplevel IDD relay, idd.unidata.ucar.edu!
> >>> Based on the latencies you and at least one other site were seeing, we
> >>> started reviewing the performance for our relay cluster.  The result
> >>> of this was some configuration changes that we are hoping have fixed
> >>> the poor reception problems you were seeing.  Given this, we appreciate
> >>> you to switching your NEXRAD2 feed back to idd.unidata.ucar.edu, at least,
> >>> for a test period of several days.  Please let us know if you are willing
> >>> to be the guinea pig for this test...
> >>>
> >>>
> >>> 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: HOA-343163
> >>> Department: Support IDD
> >>> Priority: Normal
> >>> Status: Open
> >>>
> >>
> >>
> >
> > Jeff Weber
> > Unidata User Support
> > http://www.unidata.ucar.edu
> >
> > Ticket Details
> > ===================
> > Ticket ID: HOA-343163
> > Department: Support IDD
> > Priority: Normal
> > Status: Open
> >
> 
> 

Jeff Weber
Unidata User Support
http://www.unidata.ucar.edu

Ticket Details
===================
Ticket ID: HOA-343163
Department: Support IDD
Priority: Normal
Status: Open