Thank you both Tom and Jonathan for your replies!
So far I have used integrated WMS tile caches in general. I had overlooked
the HTTP Response Headers setting, will definetely try that, That would
also be useful for basemaps created as a layer group. As I understand that
setting is not available for the moment.
Either way it seems like a difficult decision. If I go for tiled it will be
expensive during initial load and shifting between zoom levels. But I will
benefit when panning and revisiting the same areas (using client side
cache).
Victor
2013/5/8 Tom Kunicki <tkuni...@usgs.gov>
>
> Keep in mind that use tiles allows for reuse of generated tiles, either
> with server-side tile caches or client side image caching (In you Layer,
> turn on "Response Cache Headers" and set a value (seconds) under the Layer
> "Publishing" tab).
>
> Tiling has benefits if you anticipate a lot of panning (only loads new
> tiles on leading edge of panning, even without caching). If tile rendering
> is expensive caching allows for tiles to be requested and/or generated once
> (NOTE: be careful if the underlying datastore is not static). With a
> single tile the entire image bust be re-rendered and transmitted on every
> map movement (little hope of caching/reuse unless navigation is restricted)
>
> As Jonathan stated proper use depends on the client application and
> backing data. I like to use a combination of integrated WMS tile caches
> with HTTP Response Headers enabling browser caching. For use of integrated
> WMS tile caches your OpenLayers Map and WMS layer (client and server side)
> need to setup correctly have this work properly (&tiled=true, appropriate
> tie point and zoom levels, published WMS layer styles, etc). Depending on
> your workflow the effort can be worth the hassle as it will allow for very
> responsive application.
>
> Tom Kunicki
> Center for Integrated Data Analytics
> U.S. Geological Survey
> 8505 Research Way
> Middleton, WI 53562
>
>
> On May 7, 2013, at 3:16 PM, Victor Eriksen <victor.m.erik...@gmail.com>
> wrote:
>
> > Thanks for the reply Jonathan!
> > Tiling the basemaps and using singletile for overlays will probably be
> the best choice in this case, Dozens and dozens of tiles do get requested,
> slowing down for the end user as you say.
> >
> > Victor
> >
> >
> > 2013/5/7 Jonathan Moules <jonathanmou...@warwickshire.gov.uk>
> > Hi Victor,
> > From my limited experience, I don't think there's a "right" answer.
> Myself I only have tiled the base-maps. Our other layers are served
> directly from the database.
> > I guess if there are one or two layers that will be on lots more than
> most, it may be worth tiling.
> > The issue with lots of tiles is - the browser can only request a few
> images at a time (6-8 concurrent connections per server sort of thing). So
> if you have dozens and dozens of tiles, things will be going very slowly
> for the end user.
> > Others may have different opinions/experiences.
> > Jonathan
> >
> >
> >
> > On 7 May 2013 12:45, Victor Eriksen <victor.m.erik...@gmail.com> wrote:
> > Hi!
> >
> > I'm trying to figure out the best tiling strategy for overlays. I have a
> client where the user can access and view many overlays simultaneously from
> GeoServer. My present strategy is that all overlays are requested as tiled,
> some using the cache from GeoWebcache. However it seems as GeoServer is
> somewhat clogged when too many overlays are read at the same time. I guess
> accessing overlays as tiled generates a lot of requests (in comparison with
> singletile) and thus could clog down GeoServer?
> >
> > My question is, would it be a better strategy to request overlays as
> singletile in the situation when many overlays are used at the same time?
> >
> > Victor
> >
> >
> >
> ------------------------------------------------------------------------------
> > Learn Graph Databases - Download FREE O'Reilly Book
> > "Graph Databases" is the definitive new guide to graph databases and
> > their applications. This 200-page book is written by three acclaimed
> > leaders in the field. The early access version is available now.
> > Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
> >
> >
> > This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.
> >
> >
> ------------------------------------------------------------------------------
> > Learn Graph Databases - Download FREE O'Reilly Book
> > "Graph Databases" is the definitive new guide to graph databases and
> > their applications. This 200-page book is written by three acclaimed
> > leaders in the field. The early access version is available now.
> > Download your free book today!
> http://p.sf.net/sfu/neotech_d2d_may_______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
>
>
>
>
>
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
