Hi,
I've been trying out the jdbcconfig module with a data catalog of about
11,500 layers (~1000 geotiffs, a few hundred shapefiles, and the rest in
a PostGIS datastore). Immediately after the initial import of the data
catalog, the responsiveness of Geoserver seems fine, for instance when
accessing the list of layers from the administration interface and
paging through results. However, after Geoserver is restarted, or if
the configuration/catalog is reloaded from the admin interface, then it
becomes far slower - taking over 2 minutes to display each page of
layers from the admin interface.
I connected to the code running in my Tomcat instance remotely via
Eclipse and it seems that this line in the ConfigDatabase class is where
it takes so long to process:
https://github.com/geoserver/geoserver/blob/master/src/community/jdbcconfig/src/main/java/org/geoserver/jdbcconfig/internal/ConfigDatabase.java#232
The same line returns quickly immediately after the initial catalog
import. But I haven't yet been able to figure out why. Could it be
that I simply have some setting misconfigured, or that there's something
wrong with my data catalog?
-Matt
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
