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.
> We are finalizing our system specifications for the equipment grant, but have > three remaining questions: > > (1) - The specifications laid out are for 32GB of RAM on the EDEX server. > Would additional clients increase the RAM requirements? Or are there major > benefits from increasing the RAM? The more RAM the better, but we've found that 32 GB is sufficient for a standalone data server. The more clients connected and request data, the slower the response from the Request JVM, but not to a degree to make the system unusable for a classroom (from what I've seen). > (2) - Additionally, roughly how many clients can an EDEX server handle? (At > your specifications) The EDEX data request system seems more efficient than > the old X11 system, so does this help reduce RAM requirements on the server > and increase client capacity? How many clients one server can handle is still undetermined, but from experience I've had roughly a dozen clients connected to a standalone server inside a campus network and the performance has been good. > (3) - Is there any need for clients to be running AWIPS-II constantly, or can > it be activated on demand? No need for CAVE to run continuously, it can be easily stopped and restarted. Michael James Unidata Program Center Boulder, CO Ticket Details =================== Ticket ID: SSO-235746 Department: Support Egrants Priority: Normal Status: Open