On Thu, Jan 24, 2019 at 2:23 PM Arnaud L. <arnaud.lis...@codata.eu> wrote:
> What do you mean ? > The SQL view definition is the same, since it's only one single layer. > Oh dear, now I see it... and it's truly horrible! :-D I thought the various FeatureTypeStyle had a different FeatureTypeName, but it's just a different Name instead. FeatureTypeStyles are very heavy objects rendering wise, you should not use them as mere classifiers. Every time you create a FeatureTypeStyle, a new z level in the map is created. GeoServer handles it in two ways: - if possible, it tries to reuse the same data source as the previous feature type style, but to respect the z ordering it allocates a transparent rendering surface, as big as the output map, where the features captured by the rules of this FTS will be painted, and will merge the various FTS rendering surfaces at the end - otherwise, it will execute separate requests This means that even in the best of conditions, with that style GeoServer would be allocating tens of drawing surfaces, with an insane memory usage going with it (I think I see 42 FeatureTypeStyles, for a 4x4 metatile , 1024x1024, 4 bytes per pixel, that would be 168MB of RAM (you don't get that high, see below, the stacks of rendering surfaces are actually split in two). So why is it doing two queries anyways? Because you have two different names for the sortGroup, which makes the various feature type styles un-mergeable. Do yourself a favor and, if possible, use a single FeatureTypeStyle instead ;-) Cheers Andrea == 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
