Hi,
I was wondering about the rendering timeout usage in the context of the
integrated GWC.
Like, if a layer is known to be slow people will probably cache it. Ok,
given that the layer
is slow it may not be uncommon during a seed to have the rendering timeout,
if that
happens I guess we lose the tiles in question, which will have to be
rendered on demand instead,
and may end up timing out again?
I'm wondering if, for the specific case of GWC integration, we should have
a second rendering
timeout, which would be normally lax-er. Like, 60 seconds for the normal
WMS request,
but say 120 for the GWC one.
The rationale being that once a tile is cached it will save much rendering
time in the future,
so it seems reasonable to wait a bit more for the tile to be generated.
I also considered removing the limit altogether, but that seems extreme and
might
cause troubles if someone is requesting a lot of un-cached tiles in
parallel, especially
if the default style draws a lot.
What do you think?
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.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
-------------------------------------------------------
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
