Re: PGA_AGGREGATE_TARGET, AUTO PGA TARGET and WORKAREA_SIZE_POLICY

I did not cite either stack or BSS as shared.  Since you raise the topic, the stack and BSS will be roughly the same for all Oracle process images in an instance, as they all use the same "oracle" executable, with a few variations depending on dynamic libraries referenced during runtime.

The point is that the Oracle workarea management mechanism is neither monitoring nor acting based upon memory beyond the heap where PGA (and UGA) resides.

On 10/9/17 13:54, Mladen Gogala wrote:
> Actually, stack is not shared. Stack is a part of each process address
> space. And I am not at all sure that some global values for the
> process are not pushed to the stack, which would technically make them
> a part of PGA. And as for quotes around bss, that is a real segment,
> at least for the Unix/Linux implementations.
>
> https://en.wikipedia.org/wiki/.bss
>
> BSS is also not shared, because it contains initial values of
> statically allocated variables, which can probably differ from process
> to process. I have to confess that I am not quite sure about .bss
> being shared or not.
>
> Regards
>
>
> On 10/09/2017 03:41 PM, Tim Gorman wrote:
>> "Untunable" does not refer to different types of memory image segment
>> such as code, stack, and "bss", because canceling calls or killing
>> processes will not reduce the usage of code/text and shared memory on
>> the system.  Those types of memory are shared amongst processes, so
>> it would be necessary to kill *all* processes using that code/text
>> segment or shared memory segment in order to see memory utilization
>> begin to decrease.
>

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