Andrea, thanks for the detailed response! It solves the problem. Having bigger tiles (265 block was enough) made geoserver to process the file quicker.
On 08/06/11 20:28, Andrea Aime wrote: > 2011/6/8 Andrés Maneiro<[email protected]>: > GeoServer, for performance reasons, caches the image metadata, which > provide information about the image structure, such as the tile structure, > where each tile starts in the file and the like. > These image has a metadata which is massive, and results in allocating > a ton of memory for it. What I see in a memory dump: > > 9: 88107 4933992 javax.imageio.metadata.IIOMetadataNode > > 5MB only of the IIOMetadataNode class, and we still have to add its > contents, wow. > So, IIUC, although the image is 20Mb on disk, it will take more memory to geoserver to process it. How could I have a rough amount of memory needed? Is it somewhat like metadata memory + (nro of tiles * memory for each tile)? amaneiro ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
