[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[TIGGE #YSF-211129]: TCP tuning for TIGGE tuning

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.

  • Subject: [TIGGE #YSF-211129]: TCP tuning for TIGGE tuning
  • Date: Mon, 19 Mar 2007 10:03:30 -0600
Manuel,

The network route from ECMWF to CMA seems to be much better than the route
from NCAR to CMA.  My testing has been disappointing in terms of consistent
availability of bandwidth -- especially in terms of very high packet loss,
sometimes exceeding 50%.  I am trying to learn more about the network links
between NCAR and the CMA, and the changing routes.  Manuel -- can you send
me a traceroute from your system to CMA?

mike

> Hi all,
> 
> We have just installed LDM 6.6.0. Please, let us know if you experience
> any problem.
> 
> Mike, your registration to access tigge-ldm.ecmwf.int is on its way.
> 
> Ricardo Correa (ECMWF) is looking into the network bandwidth ECMWF <->
> CMA. Once we know the result, we will work into why CMA inserts 10
> GB/hour while ECMWF only receives few Megabytes.
> 
> Thanks,
> Manuel


Ticket Details
===================
Ticket ID: YSF-211129
Department: Support IDD TIGGE
Priority: Critical
Status: Closed