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.
Hi all, I'm in process of serving out some large aggregated datasets (5 - 8GB) with Thredds WMS. I consistently experience "OutOfMemoryError: Java heap space" error when making WMS requests. On my test machine, I've allocated -Xmx1536m to Tomcat and experimentally Thredds is able to serve about 1GB aggregated datasets. By digging through the Dataset Aggregation and Memory related topics on the list, I've found out that the general suggestions are to allocate more memory to Tomcat such as: -Xmx4g One post mentioned that "Thredds does everything in memory". Can somebody please advise how much memory I should allocate to Tomcat for the 8GB dataset? I'm afraid I have to secure more than 8GB memory. And what is the best practice to serve out the large datasets on Thredds in general? Regards and thanks, Xiangtan Lin Technical Services Officer | CSIRO IM&T xiangtan.lin@xxxxxxxx<mailto:xiangtan.lin@xxxxxxxx>| www.csiro.au
thredds
archives: