Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Shared Server

Status
Not open for further replies.

scohan

Programmer
Dec 29, 2000
283
US
If we are using pooled connections via web logic server (on redhat linux orcale9.2), and we route are many app users through a single oracle account, should we use oracle's shared server processes? This is fuzzy to me. I'm trying to get a handle on it, but not sure if shared server should be used with pooled connections. thanks.
 
Depends weather you want to go dedicated or shared server. Which of the 2 have you got installed.

Shared server is more efficient at OLTP systems, memory restrained etc, as less resources are taken up as instead of dedicated server processes for connection it used dispatchers. These dispatchers can be configured for connection pooling to hold thousands of concurrent users, which in total will use far less memory and resources compared to a dedicated server process.

Think of this anology. A restaurant has many customers and 1 waiter. This would be a good image of a shared server. (the waiter being the dispatcher, and the customers processes).

Compare this to customers each having their own waiter. This is a good anology of a dedicated server.

So with this being said shared servers are far more efficient.

does this help!

Sy UK
 
How to determine the maximum number of connections a dispatcher can handle? Answer ------ The maximum number of connections that a dispatcher can handle is port specific. One can see the specific number for your operating system by issuing the command: lsnrctl services P713 has 2 service handlers DEDICATED SERVER established:5 refused:0 DISPATCHER established:0 refused:0 current:0 max:60 state:ready D000 (machine: technique, pid: 29096) (ADDRESS=(PROTOCOL=ipc)(DEV=7)(KEY=#29096.1)) It is 60 in this case. Any changes you make to the sessions in init.ora are reflected in the maximum_connections column of v$mts. It is determined as: min(os_specific_limit-3, sessions init.ora parameter) The 3 are reserved for listening port, incoming connection, and tracefile. EXAMPLE ------- If your operating system supports 64 connections per process, but you set sessions to 30 in the init.ora file, then v$mts will show 30. If you raise the sessions to 100, then v$mts will show 61. The maximum number of sessions depends on both the port and on the value of sessions as set in the init.ora file.

Sy UK
 
Thanks. I still have a lot to learn. I will try to study up on this.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top