当您设计缓冲池时，您应该考虑数据库的内存需求。
When you design buffer pools, you should consider the database memory requirements.
这有助于服务器应用程序预先计算内存需求并因此而提高性能。
This helps server applications to compute the memory requirements in advance and hence increased performance.
这是由于利用率波动导致的最小和最大客户内存需求之间的差异造成的。
This is due to a large difference between minimum and maximum guest memory requirements caused by swings in utilization.
另外，这样一个彻底的构建过程对内存和硬盘的需求是巨大的。
In addition, the memory and hard disk requirements for such an exhaustive build procedure are huge.
在这种情况下，所有LPAR的工作集内存需求可以超过池中的物理内存量。
In this scenario, the working set memory requirements of all LPARs can exceed the physical memory in the pool.
对于具有大内存需求的情况，大页支持可以改善后援转换进程的性能。
For instances with large memory requirements, large page support can improve performance for the look-aside translation process.
如果用户希望访问较大的文档中前面的数个字节或数千字节，则延迟构建功能将改善该应用程序的内存需求情况。
If a user wants to access first couple of bytes or kilo bytes in a larger document, then the deferred building capability will enhance the memory requirement of that application.
如果应用程序的内存需求相对稳定，则可以考虑将堆大小的最大值和最小值设置为相同值。
If the memory requirements of your application are relatively stable, consider setting the minimum and maximum heap sizes to be equal to one another.
但是由于很难在原地进行合并，所以合并排序的内存需求比能够原地进行的排序算法(例如快速排序)更高。
But because the merging is difficult to do in place, generally, it has higher memory requirements than in-place sort algorithms, such as quick-sort.
为了进一步最小化内存需求，使用该用户界面为负载管理创建脚本。
To further minimize memory requirements, create scripts for load management using the user interface.
个别数据结构的内存需求可能会发生改变，这依赖于编译器中实现对齐的方式。
The memory requirements of individual data structures might get altered, depending upon the way packing is implemented in the compiler.
输入LPAR名称、内存和处理器需求。
每个操作系统都有自己对可用内存资源的独特需求。
Each operating system makes its own unique demands on available memory resources.
如清单4中所示，虚拟服务器模板可以包括多个资源需求元素，如CPU配额、内存和硬盘空间。
A virtual server template, as shown in Listing 4, can include several resource requirement elements, such as CPU shares, memory, and hard disk space.
考虑到这些瞬态需求，应该保留大约1gb的内存。
Approximately 1gb of memory should be reserved to account for these transient requirements.
通常，分区配置文件指定了操作系统启动时的资源需求，例如内存数量、处理器权限、适配器等等。
In general, a partition profile specifies operating system boot time resource requirements, such as the desired amount of memory, processor entitlement, adapters, and so on.
PHP的内存需求有很大的差别，取决于您网站上使用的模块。
PHP memory requirements can vary significantly depending on the modules in use on your site.
如果不小心，浏览器的内存需求将在整个浏览会话周期中不断增加。
If you're not careful, the browser's memory demands will grow over the duration of a browsing session.
从高cpu和内存需求的角度看，高容量应用程序比较糟糕。
High volume applications can be bad from the perspective of their high CPU and memory requirements.
在有超过32GBRAM的系统上，或者在使用LPAR和WPAR帮助划分工作负载的系统上，可以根据内存需求更有针对性地做出决定。
In systems with more than 32gb of RAM, or on systems where you are using LPAR and WPAR to help split your workload, you can be significantly more selective and specific about your memory requirements.
这里的优势在于，尽可能仅使用能满足用户的需求的内存。
The advantage here is that the memory is used only to satisfy user needs as much as possible.
图3展示了在应用程序的内存需求下显得力不从心的一个系统。
Figure 3 illustrates a system that is under-powered for the memory demands placed on it by running applications.
如果您的内存需求非常紧迫，则不适合使用这种占用空间较大的客户机，但是它提供了针对任何应用程序连通性场景的充分支持。
This client may not be appropriate if you have stringent footprint requirements because of its obvious size, but it does offer full support for any application connectivity scenario.
借助这些技术文档，IT管理员或者管理者可以根据实际应用来决定磁盘空间、处理器合计内存需求。
These articles help the IT administrator or manager determine disk space, processor, and memory requirements based on utilization.
这允许各进程在内存和CPU需求方面比本地OS线程更为轻量。
This allows each process to be significantly more lightweight in terms of memory and CPU requirements than a native OS thread.
如果内存需求继续增长，wlm会确保不从RAM分配新页面，而是增加分页活动。
If memory requirements continue to grow, WLM would ensure that no more new pages are allocated from the RAM; rather, there will be increased paging activity.
删除应用程序或库的某些特性，然后对其重新编译也可以降低一些内存需求。
Recompiling apps and libraries with specific features removed can also reduce their memory requirement.
由于减少了内存需求，事件API可以处理任意大小的文档，包括大小超过可用内存的文档。
Because their memory requirement is reduced, event APIs enable processing documents of any size, even documents greater than the available memory.
16MB 的页面称为大页面，16GB 称为超大页面，它们用于内存需求非常大的应用程序。
The 16MB page size is known as large and the 16GB page size as huge; both have use cases for very large memory applications.
Heap模板对于评估应用程序的内存使用和需求非常有用。
The Heap template is useful for evaluating the memory usage and requirements of your application.
应用推荐