On Thu, Jun 19, 2014 at 5:23 AM, Jody Garnett <[email protected]>
wrote:
> Kevin has been working on optimising the JDBC catalog implementation for
> large number of layers similar to what you are working with. The "catalog "
> is what geoserver uses to store all the layer names and bounds.
>
> - http://docs.geoserver.org/stable/en/user/community/jdbcconfig/index.html
> - https://github.com/geoserver/geoserver/pull/592
>
One thing that I've been wondering about jdbc is what portiong of the
speedup is due to
not having to scan the file system and read xml files, and what is due to
not checking
if feature type/coverages are valid (something that we should do for the
file system based
loader too imho, since now we have the options to have caps documents
generated in spite
of misconfigured layers/stores)
Did anybody ever measure?
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
