| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: SQL*Net tuning - what's reasonable for response times
On Wed, 19 Aug 1998 21:06:20 -0700, Austin Durbin
<adurbin_at_nsearthlink.net> wrote:
>I have a third party application that needs to connect to the database
>over a local area network and run a faily simple query to obtain a
>customer balance - all in less then 6 seconds.
>
>Some performance measurements show that 4 seconds is being
>consumed by establishing the connection (login). On average the database
>has 50 to 70 active connections at any given time with a highwater mark
>of 119 connections.
>
>Everything is running on NT 4.0 (workstation and server) and the network
>protocol is TCP/IP on 100mb ethernet. The server is a dual pentium with
>1GB of memory.
>
>Question: does 4 seconds to login seem reasonable? I've never before
>given much though to tuning connect times - my focus has always been on
>tuning queries, memory usage, etc.. Frankly, 4 seconds strikes me as not
>bad.
>
This may not necessarily be a SQL*Net/Net8 tuning issue, but rather an issue of the overhead associated with establishing a session with the database and then authentication of the user. On NT, you will be creating a new thread for this user session, and there is operating-system overhead in performing this operation.
One solution for you to investigate is Oracle MTS (Multi-Threaded Server). From the Oracle8 Concepts manual:
"The multithreaded server configuration allows many user processes to share very few server processes. The user processes connect to a dispatcher background process, which routes client requests to the next available shared server process.
The advantage of the multithreaded server configuration is that system overhead is reduced, increasing the number of users that can be supported. A small number of shared server processes can perform the same amount of processing as many dedicated server processes, and the amount of memory required for each user is relatively small."
If there is some latency in the concurrent usage of your application, you can see *dramatic* performance gains and reduced server-resource consumption with the use of MTS.
Hope this helps.
>I have been unable to track down any information regarding tuning
>SQL*Net and would appreciate any recommentations on how I can reduce
>this 4 seconds unless the consensus is that 4 seconds is exceptionally
>good performance.
>
Thanks!
Joel
Joel R. Kallman Oracle Government, Education, & Health
Columbus, OH http://govt.us.oracle.com jkallman@us.oracle.com http://www.oracle.com
 |
 |