NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

[awips2-users] Optimizing AWIPS 2 and LDM

  • To: "awips2-users@xxxxxxxxxxxxxxxx" <awips2-users@xxxxxxxxxxxxxxxx>
  • Subject: [awips2-users] Optimizing AWIPS 2 and LDM
  • From: Brian Bernard <bbernard@xxxxxxxxxxxx>
  • Date: Tue, 22 Mar 2016 20:17:07 +0000
  • Authentication-results: unidata.ucar.edu; dkim=none (message not signed) header.d=none;unidata.ucar.edu; dmarc=none action=none header.from=pelmorex.com;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23
Hello,

Does anyone have any tips on optimizing the AWIPS II EDEX server and LDM?

I mean optimizing to minimize data loss, and so data (particularly gridded 
data) is processed quickly and with reduced latency.

At the present time, I'm using a Dell T3610 workstation for my demo AWIPS II 
Edex server. It has 64GB RAM, four 512GB SSD and an Intel Xeon E5-1620 
processor with eight cores.

I find that with some of the data, the server slows down and in fact it will 
stop ingesting grib data after a couple of days. When I check the logs, I 
notice a number of core dumps that have been generated.

So, if anyone can give any suggestions, I would greatly appreciate it.

Regards,

Brian Bernard

  • 2016 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the awips2-users archives: