On Thu, Jun 12, 2014 at 11:33 AM, Stefano Iacovella <
[email protected]> wrote:
> I am not aware of a defined limit, Andrea may be the more authoritative
> person on this.
>
There are no built-in limits, but of course, the store/layers you try to
handle, the slower GeoServer will become,
as the in memory data structures are unfortunately not setup for fast
lookups, they mostly do linear scans (we should fix that).
The jdbcconfig is a community module, you can find it among the nightly
builds.
Not sure at which point it becomes faster than the in memory system,
especially for OGC requests, but if you
are using a separate database (e.g., postgis) I'd expect the threshold to
be pretty high.
Maybe the jdbcconfig developers could shed some light on its performance
characteristics.
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
