直到内存组中的值耗尽后，两个优化器才会去访问数据库，上面的例子每5个标识值符访问一次数据库。
Neither optimizer will hit the database until it has exhausted its in-memory group values. The above example hits the database every 5 identifier values.
这两组测试得到的性能结果的不同是可以预测的，因为随着数据库和分配给db2缓冲池的内存的增加，TLB缓存上的压力也随之增加。
This difference in performance gain is predictable because the pressure on the TLB cache increases as the size of the database and the memory assigned to the DB2 buffer pools increases.
事实证明，如果您虚拟化许多相同的操作系统和应用程序组，那么许多内存页面都是相同的。
It turns out that if you virtualize many of the same operating system and application sets, many memory pages are identical.
还有使用ACE 实现IPC的其他方法，比如共享内存或UNIX 风格的套接字寻址（ACE_LSOCK*组中的类）。
There are several other ways of initiating IPC using ACE, like shared memory or UNIX-style socket addressing (the ACE_LSOCK* group of classes), which this article does not address.
在这种方法中，堆分为一组卡片，每个卡片一般都小于一个内存页。
In this approach, the heap is divided into a set of CARDS, each of which is usually smaller than a memory page.
从内存的角度而言，请使用64位进程(执行组)，而不要采用32位进程。
Use 64-bit processes (execution groups) rather than 32 bit processes from memory perspective.
如果在PLAM的内存缓存中找到了组列表对应用户的PAC的版本，那么这个用户就会根据ACL的限制对所请求的对象进行授权。
If the group list corresponding to the user's version of PAC is found in the in-memory cache of PLAM, the user is granted access to the requested object based on permissions on the ACL.
尝试减少应用程序组内存。
在用户或用户组级别也能跟踪云资源（即内存、CPU、IP）的使用情况，允许CloudBurst支持整个企业拒付（Chargeback）。
Usage of cloud resources (i.e. memory, CPU, IPs) is also tracked at a user or user group level allowing CloudBurst to support chargeback across an enterprise.
最后的图表示例展示了一个包含4个不同程序内存使用的图表组。
The last chart example displays a chart group showing the memory usage of four different applications.
一个段用于应用程序组内存，因为INTRA_PARALLEL是ON。
One segment is used for application group memory because INTRA_PARALLEL is on.
在连接时，DB 2从操作系统中获取用户的组信息，并缓存在内存中。
At connection time, the group information for the user is retrieved from the operating system and cached in memory.
应用程序组共享内存集是： 40000页 *4K/页 = 160MB
The application group shared memory set is: 40000 pages * 4K per page = 160 MB
如果不使用标记组，则返回的数据将只包括在运行脚本内使用的内存，减去内存管理器开销。
Without the flag set, the data returned would be only the memory used within the running script, minus the memory-manager overhead.
至此，我们已经讨论了实例共享内存、数据库共享内存和应用程序组共享内存以及代理私有内存。
So far we have discussed the instance Shared memory, the database Shared memory, the application group Shared memory and the agent private memory.
应用程序组共享内存集没有列出，因为它是从数据库共享内存集中分配的。
Application group Shared memory set is not listed because it is allocated from the database Shared memory set.
这个问题可以通过将不完整的组临时从消息选择器中排除得到解决，也可以将该组复制到内存中或持久性存储中，以便稍后完成。
This problem can be solved by temporarily excluding the incomplete group from the message selector, or by copying the group to an in-memory or persistent store for completion later.
这使您可以有效地对多个组执行多个操作，而无需频繁将组重新加载到内存中。
This lets you efficiently perform multiple operations on multiple groups without having to constantly reload the groups into memory.
应用程序组内存集是从数据库共享内存集中分配的。
The application group memory set is allocated from the database Shared memory set.
这样做的话，您将创建额外的用户组，并且在分布式的位置中运行它们，它能够为负载提供更多的资源，例如CPU能量和内存等。
To do this, you'll create additional user groups and run them at distributed locations, which provide more resources for the load, such as CPU power and memory.
这样的逻辑同样适用于实例共享内存和应用程序组共享内存。
Same logic applies to the instance Shared memory and the application group Shared memory.
属于相同应用程序组的所有DB 2代理都使用应用程序组共享内存进行通信。
All the DB2 agents belonging to the same application group communicate using the application group Shared memory.
工具会生成一组图，查看在运行过程中的内存使用，并检查内存泄漏的指示。
A set of graphs were generated which allowed viewing of the memory usage during the run and checking for indications of memory leaks.
在每个数据处理步骤之后，设置一个PUT（将数据传输到主内存）和一个 GET（获得下一组数据）。
After each data processing step, you set up both a PUT to transfer the data to main memory and a GET to get the next batch of data.
如果数据库是分区的，或者启用了intra - parallel或连接集中器，那么数据库共享内存中有一个段被预留给应用程序组共享内存。
If the database is partitioned, or intra-parallel enabled, or connection concentrator enabled, then one segment is used for Application Group Shared Memory.
这些服务是DynaCache、内存到内存会话复制、核心组、Web服务缓存和有状态会话Bean持久性。
Those services are DynaCache, memory to memory session replication, core groups, Web services caching, and stateful session bean persistence.
应用程序在会话范围内存储了一组Place，如图1所示，并在请求范围内维护了一个Place。
The application stores a list of Places, depicted in Figure 1, in session scope and maintains a Place in request scope.
WebLogic还提供了一组选择，包括内存中(使用一个伙伴复制品)、基于文件的或者基于数据库的。
WebLogic also offers a host of choices, including in-memory (using a single buddy replica), file-based, or database-based.
这些服务是DynaCache、内存到内存会话复制、核心组、Web 服务缓存和有状态会话bean持久化。
Those services are DynaCache, memory-to-memory session replication, core groups, Web services caching, and stateful session bean persistence.
可以使用lvmo修改每个卷组的pbuf(即固定内存缓冲区)，可以显示和控制用来缓存卷组数据的内存。
Lvmo allows you to change the pbuf, or pinned memory buffers, used for each volume group, and therefore shows and allows control over the memory used to cache volume group data.
应用推荐