Re: memory per database connection on windows

I would like to add that in windows a single database instance "shares" the virtual address space with all sessions.

i.e. MTS or NOT you wont have more memory. In FACT mts is a little better as you can strictly control the UGA memory.

pga_aggregat_target is only a target and not a limit, you can easily go over.

Under windows 32 bit you will always be limited to < 3 gb memory for a single instance.

Christo Kutrovsky
The Pythian Group

On 9/15/05, Jeffrey Beckstrom <JBECKSTROM_at_gcrta.org> wrote:
> When we running Oracle 8I on Windows we implemented Multi-threaded server
> and added the /3gb switch to the boot.ini file so we could have a larger
> process size. We are now running Oracle 9I with MTS still active. I am
> considering eliminating MTS. We have pga_aggregate_target set so sessions
> would share sort memory. I am trying to located a note giving an idea of
> amount of memory per database connection to see if by eliminating MTS and
> the Large Pool if we would have a wash in terms of memory usage.
>
>
>
> Jeffrey Beckstrom
> Database Administrator
> Greater Cleveland Regional Transit Authority
> 1240 W. 6th Street
> Cleveland, Ohio 44113

-- 
Christo Kutrovsky
Database/System Administrator
The Pythian Group
--
http://www.freelists.org/webpage/oracle-l