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.
All, NCEP is indeed on internet2, which I presume would apply here. A couple of noteworthy things.... I see some latency, but not for everyone, and it doesn't seem to matter which conduit machine a client is connected to. For example, with today's and yesterday's gfs.t12z.pgrb2.0p25.f096 (hour 96) file here are the latencies per client that I see: 11/12 Another correlation is that UIUC and PSU (the ones with latency) are only using one thread to connect to our conduit, whereas Wisc. and Unidata use multiple threads. At the moment this sort of has the appearance of a bottleneck outside of NCEP. It might also be useful to see traceroutes from UIUC and PSU to NCEP's CONDUIT. I know I saw some traceroutes below. Can you try that and share with us? Mike Shedlock NCEP Central Operations Dataflow Team 301.683.3834 On 11/13/2015 11:42 AM, Mike Dross
wrote:
|
_______________________________________________ conduit mailing list address@hidden For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/