On Fri, Feb 9, 2018 at 3:24 PM, jgzurano <jgzur...@gmail.com> wrote:

> Hi Andrea, thanks for the quick reply!
> We will look into time enabled layers, I'm not sure that we're using that
> feature.
> This amount of layers is because our customers have lots of small tiles and
> are loading more everyday (around 5k daily).

Hmm.. and they cannot be loaded as additional data in an existing layer
You could add a field identifing the tile if it's vector data, or an
attribute in a image
mosaic if it's raster.
Just thinking out loud.

> We're thinking about splitting our geoserver installation into two or more
> servers (with different data_dir and database). That way we could keep the
> catalog size and number of layers per installation in a way that doesn't
> hurt the performance so much.
> What number of layers do you think it can work without losing too much
> performance?

With the default catalog I would not go beyond 50k, maybe 100k as a stretch.

> Do you think that migrating from xml files to jdbcconfig with postgresql we
> could keep increasing the amount of layers without degrading performance?

With the current code you'll likely get a constant performance penalty
compared to
the in memory catalog. But I'm not sure, beyond some tests with smaller
amounts of layers
(tens of thousands), I have not used the module in a long while.
As said, if you want to go down this path, you better get commercial


GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Andrea Aime
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



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 
- Earning your support instead of buying it, but Ian Turton: 
- The GeoServer user list posting guidelines: 

If you want to request a feature or an improvement, also see this: 


Reply via email to