Maximum Connections and consumer applications

Dave wrote:
> "Y" <ytalreja_at_comcast.net> wrote in message
> news:8b80bedf.0411031403.6f8cfdc4_at_posting.google.com...
> > Folks,
> >
> > We are running 6 instances of a proprietary application server
> > against an Oracle8 instance with a connection pool of 16 each (for
a
> > total of 96 connections). This is running on a dual proc Sun server
> > with 1 GB of memory As our volumes have ramped up, we need to
increase
> > the number of connections in the pool and the related parameters in
> > Oracle's config files. All users to the database go through these
App
> > Servers/connection pools.
> >
> > I believe I would need to increase the queuesize in listener.ora
> > file and the SESSIONS/PROCESSES parameters in init.ora file. Are
there
> > any other parameters I need to change?
> >
> > I would like to know if there is a formula to determine a "safe"
> > limit for bumping these up; i.e. if there is a rule of thumb for
> > correlating maximum number of these parameters with the # of CPUs/
> > memory size. I do realize that if I bump these up too high, I will
run
> > into the Unix limit of max. # of processes, but that typically
exceeds
> > 1024.
> >
>
> surely you know how many session / processors will be on your
database?

The product is going to support consumers so the number of sessions will vary depending upon how large we set the connection pool to be which in turn will determine the "SESSIONS" parameter on the server. We are already seeing connections refused to end users since our connection pool whose value has been determined by the "SESSION" parameter is too small. So we do know we need to bump up the size of the connection pool and hence the size of the SESSION parameter, but we do not know how large can we make it. i.e. if there was a rule of thumb.

Yogesh Received on Mon Dec 13 2004 - 18:02:45 CST