On Wed, Nov 8, 2017 at 1:39 PM, Steve Omondi <steve.omo...@ramani.co.ke>
wrote:
> Hi Andrea,
>
> I have read the proposal GISP 155 (https://github.com/geoserver/
> geoserver/wiki/GSIP-155) and the status indicates that it's completed in
> the *Geoserver-2.11-beta*. I am using *Geoserver-2.11.2*, was this
> version released with the improvement?
>
>
Yes , it part of 2.11 and 2.12. But it's an improvement for the standard in
memory catalog, not for the JDBC one.
> Otherwise from which version of Geoserver is the improvement available?
>
> Do you have some recommendations for making JDBC Catalog more performant
> for example would creating materialized views to replace the standard views
> or add some index for more used objects/tables?
>
>
Fixing the code is pretty much the only approach I'm afraid, it's not that
the queries take too much time, it's that the code is doing way too
many very small ones (query latency is killing it, not data
finding/gathering), what's missing is a layer of caching in between (there
is already one, but it's not sufficient) so
that the queries are not run.
Check the geoserver-devel archives, there is a discussion about it:
http://osgeo-org.1560.x6.nabble.com/jdbcconfig-performance-td5324352.html
So far nothing happened code wise, but it seems the way to go to fix the
jdbcconfig on typical GetMap/GetTile requests.
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
