On Tue, Feb 25, 2014 at 11:17 AM, Wilhelm, Dirk <[email protected]>wrote:
> Hi,
>
>
>
> all 6 data stores are configured like this:
>
>
>
> max connections 100
>
> min connetions 1
>
> fetch size 1000
>
> Connection timeout 20
>
>
>
> Max open prepared statements 50
>
>
>
> validate connections, loose bbox and estimated extends are checked
>
Right, in this case the prepared statement leak does not seem likely, but
you'll have to do
something to limit your memory usage (see the PDF).
Given the numbers we have, you'd need 100 (conn) * 50 (statement) * 20MB
(buffer for each statement) -> 100GB
or memory just to keep the prepared statement buffers
Limiting the fetch size and the number of cached prepared statement is a
quick way to start,
but glancing over the PDF, it seems you'll also have to work on the
definition of your table.
Alternatively, we could look into implementing a non prepared statement
version of
the Oracle dialect, which would solve the issue at the root, but that would
surely require
some days of work
Cheers
Andrea
--
== Our support, Your Success! Visit http://opensdi.geo-solutions.it 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
-------------------------------------------------------
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
