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.
Hi John, re: > Thanks Tom, > > We can't get but 100Mbs on rime.ttu.edu sorry. Hmm... Is this because the Ethernet interfaces on rime only support 100 Mbps (this would be unexpected), or is it that the switch to which rime is connected only has a 100 Mbps port open? If 100 Mbps has to be lived with, then the objective(s)/expectation(s) of the test that rime was setup for have to be changed. In particular, I think that all we can look for now is if latencies reported by rime for the IDS|DDPLUS and NEXRAD3 feeds stay low over or climb over the time interval that the feeds on mammatus climb. If they stay low, it should indicate that there is a significant different for a machine running outside and inside of your data center. This would strongly suggest that some sort of shaping is being done inside the data center. re: > But you can look at > meso-file1.tosm.ttu.edu now and see that it is also doing the same thing and > it's a > physical in the datacenter running at 1Gbs with a very close connection to > the border. This is a completely different test since meso-file1.tosm is inside of the data center regardless of its connection proximity to the border. So, let's compare the NEXRAD3 latency on rime and meso-file: rime NEXRAD3 latency http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+rime.ttu.edu meso-file1 NEXRAD3 latency http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+meso-file1.tosm.ttu.edu I think that the near zero latencies for NEXRAD3 on rime which is outside of the data center, and the high and growing latencies for NEXRAD3 on meso-file1 which is inside the data center are indicative of a significant difference for machines inside and outside of the data center. What is causing this we have no way of knowing. 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: GUQ-669331 Department: Support LDM Priority: Normal Status: Closed =================== 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.