Hi, Thank you Andrea, this is exactly what I need. I did not find this "numberMatched skip" at first because I was looking in the global WFS settings and it is located in WFS settings per layer (which is good). It may be a good idea to add a hints in the WFS settings doc that it exists ? https://docs.geoserver.org/latest/en/user/services/wfs/webadmin.html
Thanks and regards Julien Le lun. 22 oct. 2018 à 08:35, Andrea Aime <[email protected]> a écrit : > Hi Julien, > please keep reply on list, as indicated in the list usage guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > About the select(*) count, indeed clients use it to support paging and > removing it will > likely break some of them. However the standard allows to return "unknown" > in the attribute > value, and GeoServer allows this configuration on a per layer basis, check > in the publishing tab: > > [image: Selezione_408.png] > I'd suggest to disable count only in the tables that are so large that > counting would actually > cause a problem, to reduce downstream problems with clients. > Worst case the client can do a GetFeature with resultType=hits, and force > the return of counts, > but I doubt very many clients have this fallback behavior programmed in. > > Cheers > Andrea > > > On Sun, Oct 21, 2018 at 9:42 PM Julien Laurenceau < > [email protected]> wrote: > >> Hi Andrea, >> Thank you for your answer. >> My problem with paging is that if I use paging of WFS2.0 with "count" and >> "startindex", I still get a "select count(*)" on the server that is very >> costly and is probably required to gives clients the number of features. >> Even if geoserver streamed the feature on his side, I think that on >> postgres side the feature are loaded first in order to be counted. >> Do you think that deactivanting the "totalFeatures" calculation would be >> an option ? >> Thanks and regards >> Julien >> >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> >> Virus-free. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> >> <#m_2514079323084701551_m_-1980741412624936658_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> Le dim. 21 oct. 2018 à 20:43, Andrea Aime <[email protected]> >> a écrit : >> >>> Hi, >>> the WFS protocol has no way to advertise limits on the bounding box, so >>> trying to apply them would break >>> any "standard" client, only clients hand-crafted to work against our >>> service would be able to reliably extract information >>> out of it. >>> >>> The WFS protocol choice to avoid overloading the server is limiting the >>> number of features returned, and let the client >>> resort to paging if they cannot get all they want in one shot. >>> In GeoServer that setting is found under the "WFS" service >>> configuration, and normally set to a high value, like 10 millions >>> features, because the way GeoServer operaters is "streaming", meaning it >>> never loads the whole result in memory, >>> it reads a page of features, encodes them in GML and sends them out, >>> reads another page, and so on until the end. >>> Typically all you need to avoid being overwhelmed is enough database >>> connections, since they are kept open during >>> the whole output writing process. >>> >>> Since you are setting up for production, I'd suggest to also have a look >>> at these contents: >>> >>> - >>> >>> https://www.slideshare.net/geosolutions/geoserver-in-production-we-do-it-here-is-how-foss4g-2016 >>> - https://geoserver.geo-solutions.it/edu/en/adv_gsconfig/index.html >>> - https://geoserver.geo-solutions.it/edu/en/enterprise/index.html >>> >>> Cheers >>> Andrea >>> >>> >>> On Sun, Oct 21, 2018 at 5:36 PM Julien Laurenceau < >>> [email protected]> wrote: >>> >>>> Hi, >>>> I would like to protect my WFS server from overcapacity and thus I >>>> would like to be able to be able to tune the maximum "cost" of a single >>>> request. >>>> I already have a way to rate limit the number of calls so that once >>>> I'll be able to tune the maximum cost of a single request it will be easy >>>> to protect my server from overcapacity. >>>> >>>> The easiest way that I can think of would be : >>>> - to force users to define BBOX in their requests >>>> - to be able to limit a maximum BBOX area on the server. >>>> >>>> I saw that the geofence extension is able to crop the visible area to >>>> some regions, but this is not what I want. >>>> I would like everything to be visible to users, but I would like to >>>> force users to perform several requests when they would like to retrieve a >>>> lot of features with WFS. >>>> >>>> Thanks and regards >>>> Julien >>>> >>>> >>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> >>>> Virus-free. >>>> www.avast.com >>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> >>>> <#m_2514079323084701551_m_-1980741412624936658_m_-7363697846295413904_m_-5174598143498235861_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>>> _______________________________________________ >>>> Geoserver-users mailing list >>>> >>>> Please make sure you read the following two resources before posting to >>>> this list: >>>> - Earning your support instead of buying it, but Ian Turton: >>>> http://www.ianturton.com/talks/foss4g.html#/ >>>> - The GeoServer user list posting guidelines: >>>> http://geoserver.org/comm/userlist-guidelines.html >>>> >>>> If you want to request a feature or an improvement, also see this: >>>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>>> >>>> >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>>> >>> >>> >>> -- >>> >>> Regards, Andrea Aime == GeoServer Professional Services from the >>> experts! Visit http://goo.gl/it488V for more information. == Ing. >>> Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito >>> 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: >>> +39 339 8844549 http://www.geo-solutions.it >>> http://twitter.com/geosolutions_it >>> ------------------------------------------------------- *Con >>> riferimento alla normativa sul trattamento dei dati personali (Reg. UE >>> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >>> precisa che ogni circostanza inerente alla presente email (il suo >>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >>> This email is intended only for the person or entity to which it is >>> addressed and may contain information that is privileged, confidential or >>> otherwise protected from disclosure. We remind that - as provided by >>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >>> e-mail or the information herein by anyone other than the intended >>> recipient is prohibited. If you have received this email by mistake, please >>> notify us immediately by telephone or e-mail.* >>> >> > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime > @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 > Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 > 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
