Re: Shrinking PGA of snp processes

Hi Christo,

What's the _smm_max_size value for your session? It states the max workarea size for a serial session in kB (and defaults to 5% of pga_aggregate_target).

But if you want so big PGA memory areas, it might be worth using manual workarea for those sessions anyway...

Tanel.

• Original Message ----- From: "Christo Kutrovsky" <kutrovsky.oracle_at_gmail.com> To: <tanel.poder.003_at_mail.ee> Cc: "ORACLE-L" <oracle-l_at_freelists.org> Sent: Friday, May 13, 2005 9:19 PM Subject: Re: Shrinking PGA of snp processes

> Tanel,
>
> I've noticed that the growth of memory is done in steps. And those
> steps become progressivelly large, until it can no longer allocate
> memory.
>
> Even on 64 bit systems, a single workarea is limited to 4 gb. And
> because of this step allocations, allocation actually stops at arround
> 3.5 gb (instead of just under 4gb).
>
> Have you found any way to control the step, or at least the maximum
> step during step allocation ?
>
> I wonder when they will start to support the Linux hugetlb pool for pga
> mem=
> ory.
>
> I've noticed that it will never de-allocate the memory, if you are
> under your pga_aggregate_target. But once you start using it in
> another process, it will de-allocate it.

--
http://www.freelists.org/webpage/oracle-l