Hi Andrea
first: thanks for you feedback :)
I understand what you mean by having all shpefiles in one layer. The shapefiles
however belong to different users and should be displayed/treated as standalone
layers.
I see that by such amount of layers jdbcconfig is the only way? I will check
the getmap performance and share the experience with you.
Regards
Bartek
W dniu 2017-07-24 17:09:44 użytkownik Andrea Aime
<andrea.a...@geo-solutions.it> napisał:
On Mon, Jul 24, 2017 at 4:55 PM, Bartek Burkot <pomiarowie...@poczta.onet.pl>
wrote:
Thanks Edward for your feedback really appreciate
Maybe I was not clearly mentioning the problem but I'm going to register 2
million layers in geoserver and access it via getmap WMS method one by one. Not
all at once in one request.
You can still access them one by one, by adding a CQL_FILTER hitting the mosaic
index (assuming you harvested an attribute allowing you to tell them apart, it
might be even be the file name
which is already there).
I experienced the troubles with long start up time of Tomcat service if there
is many configured layers in it. In extreme case the startup time was several
hours. That's why I mentioned the jdbcConfig plugin which stores the
configuration of layers in DB instead in local filesystem. With jdbcConfig the
startup time is about several seconds instead of several hours.
Because it's not loading the catalog on startup, but querying things on demand
(and making tens of queries to the database per request).
Which, with 2 million layers, may be a quite significant overhead... when
working on the ticket you mentioned
I noticed jdbcconfig was adding 80ms overhead on all requests compared to a
catalog in memory, with a catalog of 10k layers stored in a local postgresql
database.
With 2 millions, even considering a logarithmic growth of the overhead,
assuming everything jdbcconfig queries is indexed, you might still be looking
at 1s ovehead per request (only actually trying will tell you the exact extra
time, mine is just a guess).
Has anybody of you experience by adding a huge number of layers to geoserver?
The normal approach is to avoid setting them up, and perform some filtering on
a single layer instead.
It also makes sense, since with a million layers the normal WMS protocol,
starting with capabilities,
becomes 100% unusable, so you definitely have some other way to know which item
you want
to pick out of the 2 millions.
Cheers
Andrea
--
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
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
