[Geomoose-users] caching and other ways to increase performance
Bob Basques
Bob.Basques at ci.stpaul.mn.us
Fri Jul 29 15:52:53 EDT 2011
Bob,
All old school here, we built our own raster pyramids and make a new
request every time, no caching because we want to have the option of
making incremental zoom scales.
We don't use Tiled layers at all becuse of the limitation in needing to
use a stepped view zooming (Like Google) , we need to be able to see
some things are very particualr scale values for example.
The raster pyramiding is actually doing this stepped zooming, but in
the storage of the rasters, not in the publishing of them. Since we
only ever assemble four tiles per layer on the fly, we can predict very
well what the performance should be like at all levels or scales of
operation.
We have also done some work on Load balancing the composite raster
requests across many hardware servers with good results.
With the right tunning you can make even a WMS respond very quickly,
even for very large image requests.
bobb
>>> "Bistrais, Bob" <Bob.Bistrais at maine.gov> wrote:
I was wondering what anyone was doing, with regard to caching tiles or
other ways to boost performance in GeoMoose applications? While our
current applications are performing well in GeoMoose, we’re looking
ahead as applications get more complex and bloated with data. Has
anyone done anything with GeoWebCache, for example, or some other means?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20110729/32591ec3/attachment.html
More information about the Geomoose-users
mailing list