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

[Support #GNI-177943]: Re: tigge config @ cma

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: [Support #GNI-177943]: Re: tigge config @ cma
  • Date: Fri, 30 Mar 2007 14:43:16 -0600
YangXin,

One phase of the proposed testing is complete and is a success.  We configured 
a TCP proxy on ultrazone port 8080 that redirects ldm traffic to port 388, 
changed all the ultrazone request lines on tigge-ldm.cma to request from port 
8080, and restarted the ldm.  The result is a 35-40x improvement in data 
transfer 
rates (and implies packet shaping or throttling on port 388)

http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?EXP+tigge-ldm.cma.gov.cn

We can apply these same concepts to data flowing out of CMA and ECMWF and start
that data moving as well.

Chiz has several ideas for additional LDM tuning he'd like to test as well.

mike

Ticket Details
===================
Ticket ID: GNI-177943
Department: Support IDD TIGGE
Priority: Normal
Status: Closed