Ciao Jody, in real use cases storing this values must be done with care. Most people tend to update tables directly and continuosly with incoming data (moving objects, time series) hence caching the bounds can lead to people not seeing freshest data. I would probably not cache this info by default and also I would make sure we can force a recompute via GUI/REST.
Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. On Mon, Jan 23, 2017 at 10:43 PM, Jody Garnett <jody.garn...@gmail.com> wrote: > Checking WMS 1.1.1 getcaps can have a single value, a list, or a interval - > I agree it would be good to store this (similar to bounds) rather than > calculate as you describe. > > > > > > -- > Jody Garnett > > On 23 January 2017 at 12:57, Dave Blasby <dbla...@boundlessgeo.com> wrote: >> >> Hi, >> >> I'm just starting looking into some slow downs in geoserver when adding a >> time dimension to a vector layer (i.e. postgis or geogig). By this I mean >> editing the layer, going to the "Dimensions" Tab and "Enabling" Time or >> Elevation. >> >> A. GetCapabilities gets slow. It does a table scan for each >> GetCapabilities request to determine the min/max/unique values of the Time >> attribute (depending on how you set things up on the Layer's dimension's >> tab). >> >> B. GetMap gets slow. I tracked this down to it doing 2 table scans and an >> index scan. >> >> a. It does scan of the data to determine the max time. This is likely >> because the default is to have the max date be the "default" in a query; >> >> SELECT max("datemod") FROM "public"."my_dataset" >> >> b.It does a scan of the data to construct a FID-Time Index for the entire >> dataset (for each getmap request): >> >> SELECT "gid","datemod" FROM "public"."my_dataset" >> >> c. It then does a (normal) index scan to get data required to draw; >> >> SELECT "gid",encode(ST_AsBinary(ST_Simplify(ST_Force2D("geom"), 15.5, >> true)),'base64') as "geom" FROM "public"."my_dataset" WHERE "geom" && >> <polygon> >> >> I haven't look into this in detail - but there's some obvious ways to make >> this smarter (i.e. caching time values for a layer like we cache extents - >> but that might not be what someone wants). >> >> Has anyone else looked into this? I've seen some earlier discussion, but >> nothing too concrete... >> >> Thanks, >> Dave >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
