This instructs DB2 to load some of its data into Windows' large page memory.
这指示DB 2将一些数据加载到Windows的大页内存中。
However, storing large blocks of data in application state can fill up server memory, causing the server to page memory to disk.
但是，在应用程序状态中存储较大的数据块可能会耗尽服务器内存，这会导致服务器将内存分页到磁盘。
This page then has to be read into the memory again for processing later.
那么，在以后处理这些后续页时，还必须再次将它们读入内存。
Of this existence we know many things, but no new light falls upon any page of that; in memory is written all of it that we can read.
关于现在这个存在我们知道很多，但是不再有新的光芒照亮任何一页；记忆写在我们可以阅读的所有地方。
Reverse mapping provides a mechanism for discovering which processes are using a given physical page of memory.
反向映射提供了一个发现哪些进程正在使用给定的内存物理页的机制。
The page columns show the pages of memory swapped in and out to disk.
页面列显示了从磁盘交换进来的和交换到磁盘的内存页面。
For instances with large memory requirements, large page support can improve performance for the look-aside translation process.
对于具有大内存需求的情况，大页支持可以改善后援转换进程的性能。
However, for systems in which a large number of processes are running, storing page tables in high memory can be enabled to squeeze more memory out of the low memory area.
不过，对于那些在大量进程在运行的系统来说，将页表存储到高端内存中可以在低端内存区域挤出更多的内存。
The mapping of virtual memory to physical memory occurs through page tables, which are implemented in the underlying hardware (see Figure 1).
虚拟内存到物理内存的映射通过页表完成，这是在底层软件中实现的(见图1)。
Not to complicate things, but for certain workloads, we've actually seen an increase in performance as well with a uniform page size since memory doesn't get fragmented.
为了不将事情弄复杂，而是针对某种工作负载，我们已真正看到了通过统一页面大小带来的性能增长，因为没有将内存分成几段。
By default, the system does not allocate any memory to the large page physical memory pool.
在默认情况下，系统并不为大页面物理内存池分配任何内存。
The first page of virtual memory in the kernel address space can be accessed by kernel code, but is marked as read-only.
内核地址空间中的第一页虚拟内存可通过内核代码访问，但是被标记为只读。
It also logs paging space in and outs, file page in and outs, candidate memory and memory references.
此外它还会记录分页空间的进出情况、文件页面的进出情况、候选内存和内存引用。
To resolve the page fault, the AIX kernel loads the referenced page to a location in real memory.
为了解决缺页，AIX内核会将所引用的分页加载到实际内存中的某个位置。
When the kernel pages a page out and then pages it back in, it usually indicates that there is strong demand for the page and that the page should stay in memory.
当内核将一个分页换出、然后再将其换入的时候，通常表示这个分页经常会被使用，并且该分页应该保留在内存中。
When an application references a page that is not mapped into real memory, the system generates a page fault.
如果应用程序引用了某个分页，而该分页并没有映射到实际内存中，那么系统将产生一个缺页。
Several platforms provide the ability to establish a large contiguous section of memory using memory pages that are larger than the default memory page size.
一些平台支持建立一大块相邻的内存区，以便能够使用比默认内存分页大小更大的内存分页。
Figure 1 illustrates how virtual pages in a process's address space are mapped to physical page frames in memory.
图1说明了进程地址空间中的虚拟页如何映射到内存中的物理页帧。
The virtual memory pages whose page frames are to be reassigned are selected using the VMM's page replacement algorithm.
可以使用VMM的页面置换算法来选择要重新分配页帧的虚拟内存页面。
Once a page is loaded into real memory, it is marked as unmodified.
在将分页加载到实际内存中之后，它将被标记为未经修改的。
The AIX page replacement daemons scan memory a page at a time to find pages to evict in order to free up memory.
AIX分页替换守护进程一次扫描内存的一个分页，找出要回收的分页以释放内存。
In this approach, the heap is divided into a set of CARDS, each of which is usually smaller than a memory page.
在这种方法中，堆分为一组卡片，每个卡片一般都小于一个内存页。
Although effective at limiting memory, using a huge page reservation to reduce host available memory may interfere with the host's memory management algorithms in subtle ways.
尽管有效限制了内存，使用大页面保留减少可用内存却可能对客户内存管理算法产生一点小影响。
Now, you'll build the page first in memory and then dish out the completed page to the browser.
现在，先在内存中构建页面，然后将完成的页面分发给浏览器。
TLB is the cache holding the mapping information from the virtual address to the physical page in memory.
TLB缓存包含从虚拟地址到内存中物理页面的映射信息。
Unless your database requires it, there's normally no need to have twice the page space as you have memory.
除非数据库需要，分页空间一般不需要达到内存量的两倍。
Page unload Page object is unloaded from the memory.
PageUnload页面对象从内存中卸载。
Right now, XFS for Linux requires that the XFS filesystem block size is the same size as the platform's memory page size.
目前，XFS的Linux版本要求XFS文件系统块的大小与平台的内存页面大小相同。
Starting with DB2 9, DB2 automatically detects and USES 64-kilobyte page sizes for select memory regions.
从DB 29开始，DB 2自动为选择的内存区域检测和使用64KB页面大小。
Starting with DB2 9, DB2 automatically detects and USES 64-kilobyte page sizes for select memory regions.
从DB 29开始，DB 2自动为选择的内存区域检测和使用64KB页面大小。
应用推荐