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

[LDM #XTK-117583]: optimum queue settings for mostly non IDD LDM

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: [LDM #XTK-117583]: optimum queue settings for mostly non IDD LDM
  • Date: Fri, 05 Aug 2016 14:08:56 -0600
Rodger,

> Thanks for the details. I’ve changed the /reconciliation-mode as suggested, 
> doubled the
> /server/max-latency, and ran "ldmadmin vetqueuesize”. How long should I let 
> things run
> before I double the max-latency again? It will take awhile to get to the 
> target of 3600.

The first field in the output of the command "pqmon -S" indicates if the queue 
is full (i.e., if a product has been deleted to make room for another product) 
and, consequently, if it's worth executing the command "ldmadmin vetqueuesize". 
The field will be 1 if the queue is full and 0 otherwise.

> Yes, we are using the metrics-collecting and plotting capabilities. We’ve 
> also installed
> munin to fully monitor the server and are using code provided by Patrick 
> Francis that
> collects stats from the Novra modem. It’s great being able to see plots of 
> signal
> strength and carrier-to-noise and other details on how the dish is performing.

Excellent. We do the same here.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: XTK-117583
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.