[Geoserver-devel] Out of memory on configuring very large Coverage

GeoServer GeoServer Developer
1

Hi,
I'm working on a Coverage plugin and run into a problem when trying to add a
large Coverage (~1Tb+ uncompressed).
I think the problem is in org.vfny.geoserver.config.CoverageConfig.java,
line 241 through 263 where a piece of the coverage is read to get some meta
information.
In my case this piece, 1/20 by 1/20 of the original envelope, is about
100000x100000px.

Any suggestions?

/Peter

--
View this message in context: http://www.nabble.com/Out-of-memory-on-configuring-very-large-Coverage-tf4643146.html#a13262373
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

2

peter_se ha scritto:

Hi,
I'm working on a Coverage plugin and run into a problem when trying to add a
large Coverage (~1Tb+ uncompressed).

Wow, what format is your coverage into?

I think the problem is in org.vfny.geoserver.config.CoverageConfig.java,
line 241 through 263 where a piece of the coverage is read to get some meta
information. In my case this piece, 1/20 by 1/20 of the original envelope, is about
100000x100000px.

Any suggestions?

Simone should be back from his travels today or tomorrow and should
have an idea of what to do with it... I'm not so expert in coverage
code, yet I have one possible hint.
I know metadadata can be read without actually loading the
coverage in some formats. For example, in the TIFF case the grid
coverage returned contains a JAI delayed load raster, which can
be quiried for meatadata without actually loading the pixels
from the disk.
If you're coding a new coverage reader it's very important you do
the same, all the code assumes readers are well behaved in this
respect.

Cheers
Andrea

3

Thanks Andrea,

You're right, I didn't think of that. I'll definately work on 'metadata
populating' the RenderedOp so that no reading has to take place just to
figure out dimmensions etc.
I also realize now that the reason I got out of memory is that I created a
dummy implementation of the get method using the Pattern operation (inspired
by the ImageMosaicReader wich by the way is really helpful) to generate a
result. Of coarse the pattern got huge in my case..

Best regards,

/Peter

--
View this message in context: http://www.nabble.com/Out-of-memory-on-configuring-very-large-Coverage-tf4643146.html#a13284356
Sent from the GeoServer - Dev mailing list archive at Nabble.com.