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.
=============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ =============================================================================== ---------- Forwarded message ---------- Date: Fri, 1 Sep 2000 14:43:30 -0400 (EDT) From: Arthur A. Person <address@hidden> To: Jeff Weber <address@hidden> Subject: Re: 20000831: Diagnosing data slowness at Penn State (new thread) Hi... I have a question on theoretical bandwidth limits for IDD traffic... What is the maximum bandwidth in products/second as a function of turn-around time on the network? For example, if each product transmitted to a downstream site had one turn-around wait associated with it, and the average network turn-around time were 40ms, then a maximum of 1/0.040=25 products/second could be transmitted before products would begin to backlog on any particular IDD stream. I'm asking this because I'm wondering if we might be pushing the limit on the number of products per stream into navier which ingests all of the Noaaport and NMC2 stuff on one stream (is that correct?... I'm assuming one connection to motherlode results in all products being sent serially over the network in one stream). Can you enlighten me on interproduct latencies and theoretical maximum products/second? Or am I imagining a problem that wouldn't exist? Thanks. Art. Arthur A. Person Research Assistant, System Administrator Penn State Department of Meteorology email: address@hidden, phone: 814-863-1563