This instructs DB2 to load some of its data into Windows' large page memory.
这指示DB 2将一些数据加载到Windows的大页内存中。
For instances with large memory requirements, large page support can improve performance for the look-aside translation process.
对于具有大内存需求的情况，大页支持可以改善后援转换进程的性能。
However, if you make it too large, you can waste valuable memory resources on your managed system due to the size of the page table created for the partition.
然而，如果将它设置的太大，则可能会由于为该分区创建的页表大小而浪费所管理系统上的宝贵内存资源。
By default, the system does not allocate any memory to the large page physical memory pool.
在默认情况下，系统并不为大页面物理内存池分配任何内存。
Large pages can accommodate more memory in fewer actual pages, so as more large pages are used, more memory can be referenced through the TLB than with smaller page sizes.
大内存页可以用更少的实际页来提供更多的内存，相当于较小的页大小，使用的大内存页越多，就有越多的内存可以通过TLB引用。
Note that as shown here, a process may have a large address space, but it is sparse, meaning that small regions (pages) of the address space refer to physical memory through the page tables.
注意这里的显示，进程可能有一个大的地址空间，但是很少见，就是说小的地址空间的区域(页面)通过页表指向物理内存。
Large page usage is primarily intended to provide performance improvements to memory access intensive applications.
使用大页主要是为提高内存访问频繁的应用程序的性能。
The 16MB page size is known as large and the 16GB page size as huge; both have use cases for very large memory applications.
16MB 的页面称为大页面，16GB 称为超大页面，它们用于内存需求非常大的应用程序。
I have run large Oracle databases running AIX with 250 GB of memory and three 24 GB page Spaces.
我曾经在AIX上用250GB内存和三个24 GB的分页空间运行大型Oracle数据库。
Solaris large page support was enabled, and 3300 mes of Shared memory was pre-allocated to Lotus Domino.
启用了Solaris大页面支持，并为LotusDomino预先分配了3300MB的共享内存。
The vmo command can be used to configure the size of the large page physical memory pool using the lgpg_regions and lgpg_size options.
可以使用vmo命令的lgpg_regions和lgpg_size选项配置大页面物理内存池的大小。
Large page support is provided for memory intensive applications, allowing 16mb page sizes while still providing the traditional 4kb page sizes.
为需要内存很多的应用程序提供了大页(large page)支持，允许使用16MB的页大小，同时仍支持传统的4K b页大小。
With a simple vmo change here, you can actually tune the system to provide for large page usage, which can improve system performance substantially in very memory-intensive applications.
通过下面一项简单的vmo更改，您就可以对系统进行优化以提供大型的页面，从而对于消耗大量内存的应用程序极大地提高系统性能。
On Demand Page loading (ODPL) is a feature that reduces the amount of memory used by large forms and that increases the speed of form loading and processing.
OnDemandPageLoading (ODPL)特性可以减少大型表单使用的时间，提高装载和处理表单的速度。
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 main purpose for large page usage is to improve system performance for high-performance computing applications or any memory-access-intensive application that uses large amounts of virtual memory.
使用大页面的主要目的是，提高高性能计算应用程序或使用大量虚拟内存的任何内存访问密集型应用程序的系统性能。
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.
一些平台支持建立一大块相邻的内存区，以便能够使用比默认内存分页大小更大的内存分页。
Your 592-page cookbook wouldn't make for a very large database table-almost certainly small enough to fit on a 32 MB USB memory stick.
如果把592页的烹调书保存在数据库中，它算不上非常大的数据库表；实际上相当小，用一个32MBu盘就能够保存它。
Assuming a large page size of 4 MB is used in the same example from above, that same 1 GB of memory could be mapped with only 256 page-table entries instead of 262,144.
假定在前面的中使用页大小为4MB的大内存页，同样1GB内存只用256个页表条目就可以映射，而不需要262,144个。
However, storing large blocks of data in application state can fill up server memory, causing the server to page memory to disk.
但是，在应用程序状态中存储较大的数据块可能会耗尽服务器内存，这会导致服务器将内存分页到磁盘。
However, storing large blocks of data in application state can fill up server memory, causing the server to page memory to disk.
但是，在应用程序状态中存储较大的数据块可能会耗尽服务器内存，这会导致服务器将内存分页到磁盘。
应用推荐