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.
Hi Robert, Take this all with a big grain of salt, because data flow congestion is an issue right now. With one EDEX server there is a data bottleneck when the nationwide NEXRAD level 3 feed is requested in full. The rate at which products are decoded can not keep up with the rate at which products are written to disk by the LDM, resulting in a growing message queue for processing / decoding. But here's the specs we have: at Unidata we're running EDEX on a dual quad-core (16 processor) 32-bit CentOS 5.6 machine with 16 GB of RAM but have seen it run at similar performance on a machine with 8 processors and as little as 6 GB of RAM. Again, the big uncertainty now is that one backend machine does not seem able to handle a full suite of data ingested (including the full nationwide NEXRAD level 3 radar feed) and CONDUIT remains to be seen but so far performance suggests that CONDUIT will not be handled swiftly. We will have to get the Raytheon folks involved in talks soon about adjusting the thread pool size for certain products, because as of the latest release, the thread pool size can not be increased without rebuilding the AWIPS2 RPMs. Michael > > Tom, > > Our servers are 4 years old now and I was going to go about making plans > to gradually replace them. Unidata has hw requirements for the CAVE > workstation on it's AWIPS II website, but not for the EDEX server. What > is a recommended (not minimum) hw requirement for and EDEX server? > > Thanks, > Robert Mullenax > CSBF Meteorology > > > Ticket Details =================== Ticket ID: AID-198155 Department: Support AWIPS Priority: Normal Status: Open