shared server configuration

From: Maureen English <maureen.english_at_alaska.edu>
Date: Wed, 20 Oct 2010 18:22:35 -0800
Message-ID: <4CBFA3EB.606_at_alaska.edu>



We're trying to determine the optimal parameter settings to allow us to have one of our applications connect to our database (10g) using shared server connections.

We currently have processes set to 2000. With only dedicated server connections, we have swapping problems when we reach about 1800 connections. I've always thought that connections and processes were the same thing.

I'm pretty sure I understand the concept of shared servers. I see the many shared server connections to the database, and the 3 OS processes these connections are using. That looks to me like it will definitely solve our swapping problem when we get overloaded.

What I'm confused about is whether or not we need to increase the value we have for processes. I can see in v$session that there are many sessions with the same ospid...which makes sense, those are all using the same shared server process.

We don't limit shared server sessions, just the number of shared servers. What worries me is that if we have 3000-5000 people hitting our application at the same time, how will that affect the number of processes?

I've been looking at v$process in our test database, but we don't have the volume of users in this database that we have in our production database, so it's hard to determine what's happening to processes as we increase the shared server sessions.

Any comments/suggestions?

Received on Wed Oct 20 2010 - 21:22:35 CDT

Original text of this message