每日一译【1005】SGA_MAX_SIZE

The SGA_MAX_SIZE Initialization Parameter

The SGA comprises a number of memory components, which are pools of memory
used to satisfy a particular class of memory allocation requests. Examples of memory
components include the shared pool (used to allocate memory for SQL and PL/SQL
execution), the java pool (used for java objects and other java execution memory), and
the buffer cache (used for caching disk blocks). All SGA components allocate and
deallocate space in units of granules. Oracle Database tracks SGA memory use in

internal numbers of granules for each SGA component.

SGA由许多个内存组件构成，他们是用于满足一种特殊内存级别分配要求的缓冲池。比如内

存组件包含SHARED POOL(用于分配SQL和PL/SQL执行内存）JAVA POOL（用于JAVA对象

和其它JAVA执行的内存）和BUFFER CACHE(用于缓存磁盘块）。所有SGA组件分配和回收空间

使用以粒度为单位。ORACLE数据库追踪SGA内存对于每一个SGA组件使用内部的多个粒度；

Granule size is determined by total SGA size. On most platforms, the size of a granule
is 4 MB if the total SGA size is less than 1 GB, and granule size is 16MB for larger
SGAs. Some platform dependencies arise. For example, on 32-bit Windows, the

granule size is 8 M for SGAs larger than 1 GB.

粒度大小取决于总SGA的大小。在多数平台上，当SGA大小小于1GB时，粒度大小为4MB，如果SGA

更大那个粒度大小为16MB，一些依赖于平台情况。比如，32位WINDOWS，对于大于1GB的SGA的粒度大小

为8M;

Oracle Database can set limits on how much virtual memory the database uses for the
SGA. It can start instances with minimal memory and allow the instance to use more
memory by expanding the memory allocated for SGA components, up to a maximum
determined by the SGA_MAX_SIZE initialization parameter. If the value for SGA_MAX_
SIZE in the initialization parameter file or server parameter file (SPFILE) is less than
the sum the memory allocated for all components, either explicitly in the parameter
file or by default, at the time the instance is initialized, then the database ignores the

setting for SGA_MAX_SIZE.

ORACLE数据库能限制用于数据库SGA的虚拟内存大小，以最小内存启动实例，并且可以

使用更多内存当用于扩展SGA组件的内存分配时候。如果SGA_MAX_SIZE初始化参数在参数文件

或SPFILE文件里值小于所有组件分配的内存，那么或者使用参数里的，或者使用默认值，当实例

已经初始化的时候，这种情况下它将忽略SGA_MAX_SIZE参数

For optimal performance in most systems, the entire SGA should fit in real memory. If
it does not, and if virtual memory is used to store parts of it, then overall database
system performance can decrease dramatically. The reason for this is that portions of
the SGA are paged (written to and read from disk) by the operating system. The
amount of memory dedicated to all shared areas in the SGA also has performance

impact.

对于多数系统的性能可选项中，整个SGA应当适当适合于实际内存。如果它不适合，并且

虚拟内存用于存储SGA中的一部分内容，那么整个数据系统性能将急剧下降。原因是部分的SGA

配额是通过操作系统换页（写和读从磁盘）。在SGA分配给所有共享区域的内存数量中将对性能产生影响。

The size of the SGA is determined by several initialization parameters. The following

parameters have the greatest effect on SGA size:

SGA的大小决定于几个初始化参数。SGA中以下几个参数将对大小产生影响：

DB_CACHE_SIZE    The size of the cache of standard blocks.
LOG_BUFFER         The number of bytes allocated for the redo log buffer.

SHARED_POOL_SIZE The size in bytes of the area devoted to shared SQL and PL/SQL statements.
LARGE_POOL_SIZE The size of the large pool; the default is 0.
JAVA_POOL_SIZE The size of the Java pool