[Mapserver-dev] Query efficiency

[woodbri at swoodbridge.com]

I don't think you want to build the cache unless you know it will be 
needed so you don't hurt performance and memory requirements on other 
requests.

Should the query caching be a feature of the connection or of 
mapserver itself. For example some connections may be very fast and 
not need the additional overhead of caching, like with shapefiles or 
are we assuming all connections will be inherently slower and could 
benefit from caching.

-Steve W.



On 2 Mar 2004 at 22:14, Sean Gillies wrote:

> By query caching do you mean the result of a query would be a set of 
> shapes
> rather than a set of shapeindexes?
> 
> Sean
> 
> On Mar 2, 2004, at 9:09 PM, Steve Lime wrote:
> 
> > Hi guys: The issue of query efficiency keeps coming up these days as
> > queries are not simply a means to an end. SVG, image maps etc... are
> > going to push the current code, especially with non-shapefile
> > datasources. I/we need to figure out a way to cache shapes that are 
> > part
> > of a query result set. We could use the inline feature structures to do
> > this but I worry about huge result sets, and/or could consider
> > serializing shapes to some high performance format. There are some
> > interesting possibilities with the latter. Query caching could be made
> > very efficient (e.g. queryfile/savequery CGI options) and that format
> > could be useful for regular layers too, kind of like the gd2 format.
> >
> > What do folks think?
> >
> > Steve
> > _______________________________________________
> > Mapserver-dev mailing list
> > Mapserver-dev at lists.gis.umn.edu
> > http://lists.gis.umn.edu/mailman/listinfo/mapserver-dev
> >
> 
> _______________________________________________
> Mapserver-dev mailing list
> Mapserver-dev at lists.gis.umn.edu
> http://lists.gis.umn.edu/mailman/listinfo/mapserver-dev
>