On Fri, Apr 19, 2013 at 11:56 AM, Simone Giannecchini <
simone.giannecchini@anonymised.com> wrote:
Ciao Anton,
GeoServer uses a different mechanism, check this page
http://docs.geoserver.org/latest/en/user/services/wms/configuration.html#request-limits
and look for maxRequestMemory.
I believe this is one problem that has been looked at from two different
angles.
maxRequestMemory looks at it from the server stability point of view, if I
limit the total amount
of concurrent request using control flow and set a max memory usage I can
get a system
that never (or very rarely) goes out of memory.
The capabilities declarations instead are more for the client, "how big is
the largest request
before the server starts refusing answering it?"
Unfortunately the two are a bit hard to make work togheter, since the used
memory
depends also on the number of feature type styles in the SLD, not only on
the size
of the image and the number of bands of the output image (eg.., grayscale
images take
only 1/4th of RGBA ones).
I guess this could be made to work by taking the max amount of memory,
consider
the worst case (RGBA) and compute the max square image that can be
generated,
and declare that as maxWidth/maxHeight in the caps document, just as and
advisory.
And if a SLD contains too many feature type styles, we can always demote
the renderer
to "repeated data loading" mode, so that it uses a single drawing surface,
taking more
time overall, but using less memory.
Cheers
Andrea
--
GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------