We found a bug where geoserver grows basically unbounded (32GB+) when using hdf5, while the java heap and native heaps stay small (2GB and 300MB resp). The bug still exists in the current version of netcdf-java. The main symptom is unfortunately not noticeable with JVM tooling: a lot of mmapped segments of around 64K each appear when you look on linux with pmap.
I hacked a fix in the cdm-4.6.15.jar library. A test scenario that crashed the server in minutes now runs for an hour straight without growing the process RSS size.
I logged a bug in both projects (the geoserver one is pretty minimal).
We found a bug where geoserver grows basically unbounded (32GB+) when using hdf5, while the java heap and native heaps stay small (2GB and 300MB resp). The bug still exists in the current version of netcdf-java. The main symptom is unfortunately not noticeable with JVM tooling: a lot of mmapped segments of around 64K each appear when you look on linux with pmap.
I hacked a fix in the cdm-4.6.15.jar library. A test scenario that crashed the server in minutes now runs for an hour straight without growing the process RSS size.
I logged a bug in both projects (the geoserver one is pretty minimal).