Hi Guys
We have noticed many 'common' queries to our WFS, including some very common
filter queries (As HTTP GET) to our WFS's when we run training sessions. Some
of these queries are costly (15seconds) and some are nightmare-ish-ly costly
(14 mins) for some of the more complex app schema filter queries.
As far as I can see - Geoserver doesn't produce any 'cache friendly' enabling
tags, like Etag, LastModified, Cache-Control, Expires, etc. Is there any reason
for this? Are any of those able to be tracked within the application itself? I
can make some assumptions at my end, because I dont run WFS-T and I know when
my data is updated (automated/controlled nightly workflow loads data into our
public systems), but can geoserver do any of those smarts?
We have been playing around with Apache's (2.2) mod_cache and its mem_cache
variant for a WFS, and with the hacks in place (changing the headers, and
telling it to cache everything) are getting some nice - oversimplified results,
which get cached for 15 mins.
What do others do in this regard? Can the app produce more useful metrics (not
hacked on top) to allow for better headers to be stamped on the responses?
Ultimately I am not trying to improve response times for unique queries, I am
trying to improve the response times from 'test urls' or other things that
people and bots seem to do often.
Regards,
Terry
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
