« Return to Thread: Serious scalability issues with Oncourse at Indiana U

Re: dbcp vs c3p0 (was Re: Serious scalability issues with Oncourse at Indiana U)

by R.P. Aditya :: Rate this Message:

Reply to Author | View in Thread

On Thu, Sep 06, 2007 at 07:21:40PM +0000, R.P. Aditya wrote:

> Do you have minIdle and maxIdle set? and does maxIdle = maxActive? That will
> ensure you don't create new db connections and will help you scale much
> better.
>
> We have 8 appservers and use:
>
> minIdle@...=1
> maxIdle@...=14
> initialSize@...=15
> maxActive@...=14

and we mange 200+ requests per second routinely with no problems (and the PGA
and SGA on our Oracle server is much smaller than yours)

> with 400 requests per second peak, I'm don't see why you would
> need 2400 db pool connections -- maybe 400 * 2 for safety, but you are just
> eating PGA unnecessarily with all those connections, and that memory could be
> used for SGA instead (we reduced our PGA from 512m to 256m and haven't seen
> problems).

not to mention that you will reduce the CPU usage when you have fewer client
connections to Oracle

Adi

----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.

 « Return to Thread: Serious scalability issues with Oncourse at Indiana U