Depends on your workload and your code. If your code does not hog
connections for long periods of time and the queries are fairly light-
weight, then you might only need a small handful.
On the other hand, if your code ties up connections while presenting the
user interface (not a recommended mode of operation), then you would
probably need one per user.
To tune the max connections, you might want to guess low on the number
of connections, but log how long your code waits to acquire a connection
from the pool. If it's too long, then either fix your code or increase
the connections.
-- Mark
On Tue, 2005-08-30 at 11:52 +0530, Hina Chauhan wrote:
> Dear Sir/Madam,
>
>
> I am facing a problem, if u can help me.
>
> I am uging postgres 7.4 database. In java application I am using
> connection pooling (jakarta-web server, using datasource), wherein I
> have to decide how many max connection I should use.
>
> Do we have any concept wherein we can say number of connection
> propotional to number of user OR how many users per connection can
> work.
>
> My project would be used by 100 users at a time, which may increase to
> 400 users latter.
>
>
> I am having file context.xml with following settings, Can I add some
> thing more to it.
>
> <Context reloadable="true">
>
> <!-- Default set of monitored resources -->
> <WatchedResource>WEB-INF/web.xml</WatchedResource>
> <WatchedResource>META-INF/context.xml</WatchedResource>
>
> <!-- Uncomment this to disable session persistence across Tomcat
> restarts -->
> <!--
> <Manager pathname="" />
> -->
> <Resource name="jdbc/mypostgre" auth="Container"
> type="javax.sql.DataSource"
> driverClassName="org.postgresql.Driver"
> url="jdbc:postgresql://localhost:5432/collectioninfo"
> username="bacsindia" password="bacsindia" maxActive="5"
> maxIdle="2"
> maxWait="10"/>
>
> </Context>
>
>
> Regards,
>
> Hina Chauhan
> Codec Communications pvt. Ltd.