Re: sort latch usage in MTS mode

  • From: "Zhu,Chao" <zhuchao@xxxxxxxxx>
  • To: "Rajeev Prabhakar" <rprabha01@xxxxxxxxx>
  • Date: Wed, 8 Aug 2007 16:58:54 +0800

hi, Rajeev,
    We have downgraded to 9.2 version database so I can only get the
data from statspack:
SQL> select pool, name, bytes from stats$sgastat where snap_id =
71867order by bytes asc;
SQL> select pool, name, bytes from stats$sgastat where snap_id =
71867order by bytes asc;

POOL         NAME                                BYTES
------------ ------------------------------ ----------
             fixed_sga                         2072800
             log_buffer                       65028096
shared pool  sessions                        106080008
shared pool  sql area                        109488856
shared pool  parameter table block           145676720
shared pool  event statistics per sess       184320000
shared pool  library cache                   205729832
shared pool  Fixed Uga                       283315536
java pool    free memory                     335544320
shared pool  db_block_hash_buckets          1140850688
shared pool  NETWORK BUFFER                 1300799272
large pool   free memory                    3199248456
shared pool  free memory                    3514879440
large pool   session heap                   8611911608
             buffer_cache                   6.2277E+10

15 rows selected.



On 8/7/07, Rajeev Prabhakar <rprabha01@xxxxxxxxx> wrote:
>
> Hi Zhu Chao
>
> Could you please run the following
> query and post the results :
>
> select * from v$sgastat order by 3 ;
>
> -Rajeev
>
>
>
>
> On 8/6/07, Nigel Thomas <nigel_cl_thomas@xxxxxxxxx> wrote:
> >
> >
> >
> >
> >
> >
> >
> > Zu Chao wrote: maybe not many people use MTS recently due to nearly-free 
> > RAM. But when connection# goes real high, you still have to, and we are 
> > such a user.
> >
> > Kevin Closson replied: just out of curiosity, what is "real high" in terms 
> > of connect count?
> >
> >  And another (maybe irrelevant) point: when there is a mid-tier shared 
> > connection pool, that can also act as a concentrator/multiplexer (eg I have 
> > LoadRunner tested 2000 "users" executing a realistic high volume workload 
> > with (iirc) only 100-200 real Oracle connections). Yes, I know 2000 is not 
> > "real high" :) but you can scale out this approach.
> >
> > MTS and app server shared pool have different strengths and weaknesses (for 
> > the benefit of the BAAG party - or just to stimulate more informed replies 
> > - I'll refrain from proving my ignorance by guessing what they are :-).
> >
> > Regards Nigel
>
>



-- 
Regards
Zhu Chao
www.cnoug.org
--
//www.freelists.org/webpage/oracle-l


Other related posts: