Justin,
Thank you for your reply and it answers my question. I haven't looked into the
JNDI datastore option for postgis so far. Looks like that is something which
will do the trick for me. Meanwhile I am planning on running a crontab to
remove
connections sitting idle for a while(though there is some new data connection
cost involved with this approach).
Thanks,
Ravi.
________________________________
From: Justin Deoliveira <[email protected]>
To: Ravi Pavuluri <[email protected]>
Cc: [email protected]
Sent: Fri, February 4, 2011 12:21:36 PM
Subject: Re: [Geoserver-users] PostGIS DataStore RAM usage:Limit max connections
Hi Ravi,
Not sure I fully understand the concern. If you have a connection pool in
geoserver configured with a min of 35 and a max of 100, only more than 35 will
be used if needed, and additional connections will be used on demand. If your
load goes up more connections will be used... and they do take a while to be
released as they sit idle in the pool for some time. But eventually they will
be
given back, or reused if your load goes up again in the short term.
As you said I don't think you want to limit the connections on the server side
or else you won't eb able to handle the higher loads. What you can do is use a
jndi data source and configure your stores to use it, rather than having each
data store use its own data source/ connection pool. And then you can configure
it however you please. And if you need to you can configure the connection pool
to release idle connections more quickly so that the resource on the server
side
is freed up.
-Justin
On Thu, Feb 3, 2011 at 11:28 AM, Ravi Pavuluri <[email protected]> wrote:
Hi,
>
>I am using a PostGIS database which servers 50 stores(in geoserver) and each
>store contains around 7 layers(indexed). I could expect traffic(minimal) only
>to
>particular stores at a give time. I also expect that there wouldn't be more
>than
>"5 unique store" visitors at any point of time(total of 35 active
>connections).
>
>My concern here is there would be several idle postgis/postgres connections
>consuming up the RAM for stores just visited once and lying there for ever
>until
>I reach 100 connections limit from postgres.
>
>If I limit the max connections in geoserver, I would end up thrashing
>connections for each layer request within a store. Is it a good idea(in
>general)
>to limit the connections in postgres to 30-50 instead of default 100 for my
>case? I just do not want to blow away my RAM for idle connections.
>
>I have "Feature type cache size" in geoserver to maximum number of
>features/layers.
>
>
>Thanks,
>Ravi.
>
>
>
>
>------------------------------------------------------------------------------
>Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>Finally, a world-class log management solution at an even better price-free!
>Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>February 28th, so secure your free ArcSight Logger TODAY!
>http://p.sf.net/sfu/arcsight-sfd2d
>_______________________________________________
>Geoserver-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
