[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 12:36:56 -0600
Hi Brad,
re: thinking about how to cut down on the volume of data you are requesting
to lower the data latencies
> Thanks I don't need shef or hydro but I don't think I can't exclude those
> only can I?
If you knew the Product IDs for the products you don't need/want, you
could refashion your REQUEST line(s) to ask for everything except them.
re:
> I'd like just obs sat radar grid but I think that's what I have
Correct, that is pretty much what you now have. The volume of the data
you are requesting can be seen from the 'Cumulative volume summary'
link at the bottom of the real-time stats page that shows the various
feeds you are getting:
Real-time Statistics for demo1.raytheon.com [ LDM 6.8.1 ]
http://www.unidata.ucar.edu/cgi-bin/rtstats/siteindex?demo1.raytheon.com
Cumulative volume summary
http://www.unidata.ucar.edu/cgi-bin/rtstats/rtstats_summary_volume?demo1.raytheon.com
Here is a snapshot of what the cumulative volume summary stats looks like:
Data Volume Summary for demo1.raytheon.com
Maximum hourly volume 1254.518 M bytes/hour
Average hourly volume 690.654 M bytes/hour
Average products per hour 59555 prods/hour
Feed Average Maximum Products
(M byte/hour) (M byte/hour) number/hour
HDS 226.407 [ 32.782%] 395.544 19491.000
NEXRAD3 161.105 [ 23.326%] 343.439 11366.800
NGRID 146.889 [ 21.268%] 314.567 2781.000
NIMAGE 126.131 [ 18.263%] 226.263 124.400
IDS|DDPLUS 30.120 [ 4.361%] 45.029 25760.400
EXP 0.002 [ 0.000%] 0.003 31.800
When the NGRID model data starts coming in, however, relative order
for data volumes will change. Compare, for example, the cumulative
volume summary for your current upstream feed host:
Data Volume Summary for oliver.unidata.ucar.edu
Maximum hourly volume 13408.343 M bytes/hour
Average hourly volume 7316.319 M bytes/hour
Average products per hour 228160 prods/hour
Feed Average Maximum Products
(M byte/hour) (M byte/hour) number/hour
CONDUIT 3285.748 [ 44.910%] 6663.636 70837.455
NEXRAD2 1766.630 [ 24.146%] 2323.125 43592.477
NGRID 722.346 [ 9.873%] 1453.509 15722.295
NEXRAD3 675.656 [ 9.235%] 865.673 40268.000
FNMOC 292.891 [ 4.003%] 1786.549 2539.773
HDS 256.285 [ 3.503%] 432.490 17892.364
NIMAGE 125.312 [ 1.713%] 226.992 164.045
FNEXRAD 90.831 [ 1.241%] 114.304 71.295
IDS|DDPLUS 40.907 [ 0.559%] 52.820 36233.773
EXP 29.589 [ 0.404%] 62.241 310.750
UNIWISC 22.777 [ 0.311%] 30.353 25.864
DIFAX 3.434 [ 0.047%] 12.800 4.682
FSL2 1.563 [ 0.021%] 1.709 22.341
GEM 1.355 [ 0.019%] 13.477 185.364
LIGHTNING 0.995 [ 0.014%] 1.662 289.977
Notice that over a sufficient length of time, NGRID's volume is
about 70% of the volumes for all of the other data feeds you
are REQUESTing combined:
NGRID 722.346
NEXRAD3 675.656
HDS 256.285
NIMAGE 125.312
IDS|DDPLUS 40.907
--------
1098.160
My point is that if you turned off the REQUEST for NGRID data, you
would save a LOT of bandwidth. You may want to consider this if
the network congestion gets critical.
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