[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #GOE-694008]: Request for temporary IDD for NWA Demo
- Subject: [LDM #GOE-694008]: Request for temporary IDD for NWA Demo
- Date: Mon, 17 Oct 2011 11:10:33 -0600
Hi Brad,
re:
> OK the feed is coming in, I need to get some things setup still for your
> statistics, so give me a bit on that
I see that you now have real-time statistics reporting setup and working:
http://www.unidata.ucar.edu/cgi-bin/rtstats/siteindex?demo1.raytheon.com
A quick check on latencies shows that the bandwidth to your machine is
not as robust as one would like. In particular, the latencies for
the HDS, NGRID and NEXRAD3 feeds look problematic:
HDS
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?HDS+demo1.raytheon.com
NGRID
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NGRID+demo1.raytheon.com
NEXRAD3
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+demo1.raytheon.com
This kind of latency is what we have routinely experienced during demos at
booths at a variety of venues in the past. Ordinarily, I would advise you
to split your data feeds (to get around possible per connection-based bandwidth
limiting), but the LDM log file entries on your upstream feed host,
oliver.unidata.ucar.edu, show that you have separate ldmd.conf REQUEST lines
for each feed you want. Given this, I don't know if there is much of anything
we can suggest to help mitigate the situation.
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: GOE-694008
Department: Support IDD
Priority: Normal
Status: Closed