NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daryl, In regards to NOAAPort: NCF maximum latency . . . the time the product spends on queue at the NCF uplink . . . was 62 seconds since 2 Feb. Average has been 2 seconds on the NCF NWSTG queue. This is quite good . . . especially considering latencies on EMWIN is upwards of 15 minutes for "emergency" products, and hours for imagery. Also, since the first of the year, the NWSTG traffic has exploded from a little over 4GB per day to 5.9GB per day (O.K. - let's just call it 6GB per day) - 50% increase. Amount of time a product spends on a "queue" after downlink is vendor and location specific. Here are some stats pertaining to NCF latency: - -------------------------------------------------------------- channel stats reset on Sun, 02 Feb 2003, 22:03 GMT - -------------------------------------------------------------- Time on Queue Statistics - Units are in seconds, for - -------------------------------------------------------------- Channel | NCF Max | NCF Ave | NCF Max WMO - -------------------------------------------------------------- GOESEast Queue 3 1 TIGN04 KNES 050045 GOESWest Queue 93 32 TIGF01 KNES 061700 NWSTG Queue 62 2 YTUI98 KWBE 041800 DCP Queue 152 4 ZUSE86 KWBE 061200 - -------------------------------------------------------------- IDD latency will undoubtedly be landline (internet) or IDD receive system related. - -- Stonie Cooper Planetary Data, Incorporated (402) 782-6611/(770) 713-6763 On Sunday February 9 2003 06:17, Daryl Herzmann wrote: > Hi, > > Just a FYI. You may want to check out your data files for Saturday. If > you don't allow latencies over an hour (-m), you are missing data. My feed > has been running 60+ minutes behind since Saturday afternoon. Checking > out the current IDD latency charts, everybody is behind. Perhaps > something is up with NOAAPORT? > > Later, > Daryl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+RmUY3iTdV0m17SQRAt2nAJ9BaJ7J6G1yH8OX/1Wu2DKPRwgCvACfUAJB wXKl1hDSgJi6Y2JWL74g9ZY= =uiyi -----END PGP SIGNATURE-----
ldm-users
archives: