Re: sort latch usage in MTS mode

It's only the UGA part that is allocated from large pool (but it still can be used by a different bits like PX message queues though).

Workarea memory (sort/hash) gets allocated "as usual" - from PGA memory of the shared server process, not large pool.

On 8/6/07, Zhu,Chao <zhuchao_at_gmail.com> 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.
> We experienced huge "latch:shared pool" contention in 10.2 MTS environment,
> while on 9i it was fine. And we *guess* it is mainly from sort/hash, which
> will allocate memory/deallocate from large pool, and large pool is managed
> by shared pool latch.
> From statspack, the top functions that called shared pool latch is: kghalo,
> and kghfre.
> Also we are running with sort-area-size. no work-area-size-policy auto
> (though 10g start to support that).
> Anyone has experience with MTS/shared pool latch?
>
>
> --
> Regards
> Zhu Chao
> www.cnoug.org
>

-- 
Alex Fatkulin,
The Pythian Group,
http://www.pythian.com/blogs/author/alexf/
--
http://www.freelists.org/webpage/oracle-l