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.
>From: "Patrick L. Francis" <address@hidden> >Organization: BGSU >Keywords: 200510312116.j9VLGv7s008531 IDD Hi Patrick, >latency issues have arisen for me again... I >can only assume it is BGSU problems > >note two topology maps >http://weather.bgsu.edu/files/chiz/nimage.gif >http://weather.bgsu.edu/files/chiz/rtstats_topogif.gif > >and standard latency graphic >http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NIMAGE+unidata.bgsu.ed > u After looking at the latency plots for unidata.bgsu.edu on the rtstats pages, I am left with the conclusion that your ingest problem is probably at or near BGSU (I conclude this since other sites feeding from the same upstream IDD nodes as you are not showing the same latencies). >i have since cut ngrid off again to lighten the >load... servers are all less tan 0.5% cpu load. The rtstats latency plots do not look like the classic case of packet shaping that we have seen at a number of sites. I do note, however, that the latencies have gone down over the past couple of hours. Perhaps we should monitor the situation to see if it clears up by itself. Cheers, Tom -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.