Title: RE: Middle Tier spawning sessions, possible performance issues
Anjo,
 
Actually I saw this in your (et al) famous YAPP paper.
 
Still curious,
Steve
 
-----Original Message-----
From: Orr, Steve
Sent: Thursday, January 30, 2003 10:32 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Middle Tier spawning sessions, possible performance issues

I read somewhere that for apps that constantly logon/logoff (like web apps), one possible thing to do is increase the cache size for the AUDSES$ sequence. Anyone done this and seen improvements?


Curiously,
Steve Orr


-----Original Message-----
From: Anjo Kolk [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 9:15 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: Middle Tier spawning sessions, possible performance issues


You are kind of on the right track. The number of sessions doesn't really
matter. What matters is that they logon/logoff all the time. That is the
worst thing that you can do in an Oracle database. Why? The session will
allocate the cursors, parse them, close them everytime the session will
logon/logoff. The symptoms that you will see. Latch contention (shared pool,
library cache), shared pool fragmentation etc.

Anjo.


On Thursday 30 January 2003 05:14, [EMAIL PROTECTED] wrote:
> I'm far more of a developer than a DBA, but when someone told me this it
> set off a big red light in my head.
>
> We are using an Oracle Backend with a .net front front. One of our .net
> guys told me that the middle tier they are using 'spawns' sessions.
>
> We have 2 pretty distinct skillsets here so fixing the middle tier is
> probably way beyond my pervue. However, they told me that in a recent demo,
> the performance degraded overtime. Its my understanding that generally this
> is caused by one of two things.
>
> 1. Failure to use Bind Variables... we are using them everywhere.
>
> 2. Too many sessions.
>
> Am I on the right track here? How much would shared server mode help? This
> may be an enormous issue since they are expecting 250 contiguous users.
> Another option I tossed around was moving as much logic from the client
> side to the database to avoid the session spawning. I know that generally
> this is a good idea, but its difficult when the database people are lousy
> in C# and the .net people our lousy in PL/SQL and SQL.
>
> Any opinions?

--
----------------------------------------------------------------
Anjo Kolk
http://www.oraperf.com

--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Anjo Kolk
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to