Carlos Fernando Gonçalves ha scritto:
Hi Aime.
Hi. Please use the geoserver users mailing list for questions.
The things that come up in this kind of discussion may be useful
for others too.
I would like to know where I can find an information on the memory consumption RAM for the GeoServer?
It reall depends on what you're doing. Generally speaking, Geoserver will try to stream whatever it can, this means that will flow from
data stores to the users with minimal buffering.
Memory is held for WMS, in order to store the images that are being rendered, so consider the size of a typical 32bit per pixel image, by the number of pixels, per concurrent request.
A 1024x768 image will take up 3MB, for example. But if you can work with
256 colors images (see blog.geoserver.org), only 1/4 of that space will be used.
Then, the JAI cache must be taken into consideration. If you're serving
imagery, better have it big enough to contain the most requested parts of your imagery, in order to avoid hitting the disk (say, 256MB for
the JAI cache).
All in all, you should be able to get along with 512MB of RAM for Geoserver pretty well, which means, have a server with 1GB of physical RAM (since you'll need some for the operating system, an eventual
spatial DBMS, and so on).
Oh, in the computation I have taken into consideration the JVM overhead, that is the memory for the virtual machine, the bytecode,
and the JIT compiled native code, which may vary between 64 and 128MB.
Hope this helps
Cheers
Andrea Aime