Books for you

The request and response queues, as well as the session state, require additional
memory in the SGA, so in older Oracle releases, youwou ld allocate more memory
manually if you were using shared servers. By default, the memory for the shared
server session state comes from the shared pool. Alternatively, youcou ld also configure
something called the large pool as a separate area of memory for shared servers.
(We introduced the large pool in Chapter 2 in the ???Memory Structures for an
Instance??? section.) Using the large pool memory avoided the overhead of coordinating
memory usage with the shared SQL, dictionary caching, and other functions of
the shared pool. This allowed memory management from the large pool and avoided
competing with other subsystems for space in and access to the shared pool. Since
Oracle Database 10g, shared memory is automatically managed by default. Oracle
Database 11g introduced automated memory management of the SGA and PGA size
by default when you set the MEMORY_TARGET initialization parameter.


Pages:
162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186