On Fri, Mar 9, 2018 at 12:20 PM, Niels Charlier <[email protected]> wrote:
> Hello Andrea,
>
> Thanks for your answer.
>
> As far a the second issue is concerned, I have partly diagnosed it and
> reported it on jira with a sample: https://osgeo-org.atlassian.
> net/browse/GEOT-5958. It has nothing to do with performance and can be
> dismissed in this discussion.
>
Good report, thank you.
> As far as the first issues is concerned. I said it wrong in my previous
> email. As you can see by the red on the right side of the first graph, the
> exception does eventually pop up on 2.10.1 as well, but much later. We
> believe that there is no leak, but that this issue is purely performance
> related. Because the frequency of requests that require a connection is
> higher than the duration that each of those requests holds the connection
> open, geoserver eventually runs out of connections. If you look at the
> green lines of the graph, you can see that the response times in 2.11.2 are
> on average considerably longer than in 2.10.1. Furthermore, I have looked
> at jdbc and postgres related commits between the two versions and I see
> nothing that could introduce a leak.
>
> Since it is performance related, it is hard to reproduce this with a
> sample dataset. The issue does not occur in any of our Postgres layers in
> particular, but with all of them in general.
>
> Is it possible that for example the rendering time has increased, keeping
> the connections open?
>
Anything is possible, but I don't have reports of slowdowns internally in
GeoSolutions, not outside of it (that I can remember of, at least).
Wondering, do you have the "on the fly simplication" option on, at the
store level? It helps in some workloads, and hinders others
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
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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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
