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

20050610: LDM Latency Issues at UND (cont.)

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: 20050610: LDM Latency Issues at UND (cont.)
  • Date: Fri, 10 Jun 2005 16:33:08 -0600
>From: address@hidden
>Organization: UND
>Keywords: 200506101422.j5AEMiZu001122 IDD CONDUIT

Hi Rhesa,

>We're still having some latency issues with the CONDUIT data on ldm. 

We noticed that your switching to feed directly from atm.geo.nsf.gov
did not solve your problem.  We concluded that the problem was
somewhere at your end.  Given that the latencies for IDS|DDPLUS
on the same machine are near zero, my first guess would be that there
is some sort of "packet shaping" being done.

>We're concerned that the problem is that the computer that is ingesting
>the ldm feed is getting overloaded.

If your computer was not keeping up, it would show up in latency plots
for other data.

>We'd like to try having another
>computer to ingest the CONDUIT and the craft feed.  Is there a comupter
>that we can add maggie.rwic.und.edu to?  Thanks.

I think that the first thing to do is investigate possible packet
shaping at UND (or your department).  You can certainly feed CONDUIT
to maggie.rwic.und.edu from atm.geo.nsf.gov, but I don't think it will
solve your problem.

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.