Hi Everyone,
I am working a patch on the "Honour the configured BBOX" with geoserver wms
module. And we found that the number of database queries could reduce
significantly with the BBOX to filter out the useless query. And it do improve
the performance lots.
So far, I am trying to put this BBOX application option into the configuration
file. I noticed that there are few choice:
1. ApplicationContext.xml.
2. Wms.xml
3. Global.xml
Could someone suggest that which one will better to suit and what’s best way to
add this option. A code snippet will be even great.
Lingbo
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, 24 February 2015 10:01 AM
To: [email protected]; [email protected];
[email protected]
Cc: [email protected]; Tey, Victor (Mineral Resources,
Kensington)
Subject: Re: [Geoserver-devel] [ExternalEmail] Re: Propose to add an option for
latLongBoundingBox range checking before database query.
Regarding the "Honour the configured BBOX" , I summarized the pros and cons as
below. And please add into it if you like . Let’s have a further discussion.
Pros:
should be good for CSV which can't be indexed.
lazy users may have database tables without spatial indexes.
but you are correct if you can tell up front that there is no data in the
provided bounds you could avoid instantiating a datastore completely.
And obviously the check should only stop the queries if BBOX is totally outside
the data extents.
Cons:
concerned about feature bloat
it still seems an optimization for a somewhat narrow use
Cheers,
Lingbo
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Andrea Aime
Sent: Saturday, 7 February 2015 4:25 AM
To: Rahkonen Jukka (MML)
Cc: Tey, Victor (Mineral Resources, Kensington); Jiang, Lingbo (Digital,
Marsfield);
[email protected]<mailto:[email protected]>
Subject: Re: [Geoserver-devel] [ExternalEmail] Re: Propose to add an option for
latLongBoundingBox range checking before database query.
On Fri, Feb 6, 2015 at 8:18 AM, Rahkonen Jukka (MML)
<[email protected]<mailto:[email protected]>>
wrote:
I believe that for most non-buggy datastores which support indexes the queries
outside the data bounds are very fast. But the "Honour the configured BBOX"
should be good for CSV which can't be indexed. And lazy users may have database
tables without spatial indexes, or SQL view, or the filter in WMS/WFS request
creates such SQL queries which make the database backend to cease using spatial
index. And who knows what a cascaded WMS/WFS server sends back when the BBOX is
unreasonable, and network latency may make it slow to get even a valid, empty
response. All this makes me think that the "Honour the BBOX" might indeed be a
good thing to have for some configurations.
I'm still somewhat concerned about feature bloat (this will likely appear in
the UI, probably in the layer config panel) and maintenance
of the resulting code... it still seems an optimization for a somewhat narrow
use case (and the real reason is not even an optimization,
it's working around interaction with a closed source product).
Anyways, if others think it's useful, let's have it, and hope users won't use
it too much to hang themselves :-p
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
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.
-------------------------------------------------------
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
