Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: Dedicated Vs. Shared Server Mode

Re: Dedicated Vs. Shared Server Mode

From: Pete Sharman <>
Date: 12 Jul 2002 09:49:56 -0700
Message-ID: <>

In article <82xX8.62383$>, "Ryan" says...
>Someone I work with told me that you should not even consider shared server
>until you have atleast 200 concurrent users.
>Is this a good rule of thumb?

There's no such thing as a good rule of thumb, as a rule of thumb! ;)

Seriously, Shared Server does two things as far as I can see:

  1. It allows you to use some functionality that would not otherwise be available (like Connection Manager and connection pooling)
  2. It gets around resource shortfalls by having fewer processes at the back end.

It's NOT a performance improver generally. Think of all the work involved in a Shared Server circuit (user request -> dispatcher -> shared server queue -> shared server -> response queue -> dispatcher -> user). That's a lot more overhead than user request -> dedicated server -> user.

My 2 pennies worth (since I'm in the US).

>"D.Y." <> wrote in message
>> (Chris Forbis) wrote in message
>> > That is one of those fun questions you can get all sorts of answers
>> > for. But dedicated is always faster if setup correctly. But
>> > dedicated needs more resources. Now it looks like if all that will
>> > use it is WebSphere, well that is not that many connections. So
>> > dedicated seems the best with the information you provided.
>> >
>> If the number of concurrent sessions is relatively small dedicated
>> servers will work just fine.
>> > wrote in message
>> > > I am creating an initial db with the Oracle Network Configuration
>> > > Assistant.
>> > >
>> > > I am now wondering if I should install the db in Dedicated or Shared
>> > > Server Mode:
>> > >
>> A dedicated server only serves one session. A shared server can serve many
>> sessions. If there are going to be a large number of concurrent sessions,
>> MTS.
>> > > The DB is to be serving a WebLogic J2EE Application Server which is
>> > > talking to it via JDBC. This will be the only client that will be
>> > > queries to the db.
>> > >
>> > > So, in which mode should I install the db in this case? If in Shared
>> > > should I use Connection Pooling and if so, what would be the values
>> > > might suggest to use with it?
>> > >
>> Connection pooling really won't give you more active connections. Shared
>> servers will. But since WebLogic allows you to easily create connection
>> you might as well use it, so that you don't have to keep opening and
>> connections. Just pay attention to some minor details. A common mistake I
>> seen is not closing the ResultSet before releasing a connection. Then
>> quickly reach the maximum number of cursors.
>> > > Regards,
>> > > Peter

HTH. Additions and corrections welcome.


SELECT standard_disclaimer, witty_remark FROM company_requirements; Received on Fri Jul 12 2002 - 11:49:56 CDT

Original text of this message