Hi!
At the least the wording is incorrect, a user who
*connects* to instance, doesn't allocate any sort memory unless there is a need
for sort. And if there's need for 100k, only that much will be allocated. And
when the sort is over (and rows returned), the sort memory is
freed.
On the other hand, if all of the 10 users do huge sorts
with sort_area_size 100M, they could have 1GB allocated altogether, even more
than that, check my other mail. So yeah, this could introduce paging if having
not enough memory.
Btw, in mixed environments you could set sort_area_size to
small value and create logon trigger which sets s_a_s big for reporting users..
just a thought about swapping issues...
Tanel.
|
Title: Message
- SORT_AREA_SIZE question Bart Kersteter
- RE: SORT_AREA_SIZE question David Wagoner
- RE: SORT_AREA_SIZE question Nigel Bishop
- RE: SORT_AREA_SIZE question DENNIS WILLIAMS
- RE: SORT_AREA_SIZE question Farnsworth, Dave
- Re: SORT_AREA_SIZE question Darrell Landrum
- RE: SORT_AREA_SIZE question Regis Biassala
- RE: SORT_AREA_SIZE question Rajesh . Rao
- Re: SORT_AREA_SIZE question Tanel Poder
- Re: SORT_AREA_SIZE question Tanel Poder
- RE: SORT_AREA_SIZE question Bart Kersteter
- RE: SORT_AREA_SIZE question DENNIS WILLIAMS
- RE: SORT_AREA_SIZE question John Kanagaraj
- RE: SORT_AREA_SIZE question Rajesh . Rao
- Re: SORT_AREA_SIZE question Tanel Poder
- Re: SORT_AREA_SIZE question Binley Lim
- Re: SORT_AREA_SIZE question Rajesh . Rao