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

[THREDDS #WVA-198552]: NAS Hardware for Thredds Server

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: [THREDDS #WVA-198552]: NAS Hardware for Thredds Server
  • Date: Tue, 16 Feb 2016 14:35:13 -0700
Christof,

Most of the buffering is done in memory. This doesn't imply that thredds 
necessarily needs a lot of memory (2 GB can be fine, if a little cramped), 
though more memory always helps. There are a couple processes that do use the 
disk:

1) The TDM, which is a separate daemon you can run for indexing GRIB files, 
writes indexes for GRIB files to disk
2) NCSS, when returning NetCDF4 formatted data, has to first write the data to 
a temporary file on disk. This file is then returned.

I hope this helps.

Ryan

> We actually decided to run the server on a virtual server, which is hosted by 
> our IT-group. This actually brings me to another question.
> Do the different THREDDS-Services (e.g. subsetting, …) „buffer“ the data on 
> the machine on which the server is running? In other words…
> Does the virtual machine (which hosts the server) need a lot of memory or do 
> the services work directly in the directory where the data is
> located? I hope that this sounds somehow reasonable ;)



Ticket Details
===================
Ticket ID: WVA-198552
Department: Support THREDDS
Priority: Emergency
Status: Closed