面临的挑战是，程序运行的堆内存。
The challenge is that the program is running out of heap memory.
此内存不是clr托管堆内存。
这两项技术使人们有可能避免堆内存分配。
These two techniques make it possible to avoid heap memory allocation.
例如，健康指示器可以用来跟踪数据库堆内存的消耗量。
For instance, a health indicator is used to track the consumption of the database heap memory.
分析器中的堆内存值仅会增加，而永远不会减少。
The heap memory value in the Profiler will only increase, never decrease.
如果您的应用程序出现了内存泄漏，堆内存使用量将随时间稳步增长。
If a memory leak is present in your application, the heap memory usage steadily increases over time.
因此，随着可用堆内存的减少而导致更频繁的垃圾回收，性能可能会降低。
As a result, performance can degrade as the decreased available heap memory leads to more frequent garbage collection.
第一次收集后，自由堆内存主要是一些曾经的活对象(现在已死)的结果。
After the first collection, free heap memory is primarily the result of objects that were once live but are now dead.
对象从堆中分配；因此，使用的和空闲的堆内存数量是两个非常重要的统计信息。
Objects are allocated from the heap; thus the amount of heap memory both used and free are two very important statistics.
HighMemory策略下，当堆内存使用率长时间处于高位时对活动进行计量。
The high memory strategy activates metering in the event of prolonged high heap memory usage.
通过使用LDR_CNTRL环境变量，让应用程序的数据和堆内存使用大页面。
LDR_CNTRL environment variable is used so that the application's data and heap segments should use large pages.
在第2代收集时，用更多CPU周期和堆内存来换取更短的用户界面停顿时间。
This is done by trading a little bit more CPU cycles and heap memory usage for shorter UI pause time when doing gen 2 collections.
与编写普通的基于堆的应用程序相比，使用非堆内存的NHRT编程使工作量大大提高。
NHRT programming with nonheap memory creates significantly more work compared with writing regular heap-based applications.
传统GC实现使用stop - the - world (STW)方法来恢复堆内存。
Traditional GC implementations use a stop-the-world (STW) approach to recovering heap memory.
实现时采用红黑树管理所分配的堆内存，理论推导和实验表明其具有较高的效率。
To cope with the problem of heap memory leak, this paper presents a dynamic memory leak check technology based on red-black tree.
代理私有内存的常见消费者是排序堆内存，代理在查询执行期间使用这部分内存来对记录行进行排序。
The typical consumer of agent private memory is the sort heap memory that is used by the agent to sort rows during query execution.
图11演示了TuningFork所生成的gc性能概要图，包括目标利用率、堆内存使用和应用程序利用率。
Figure 11 shows the GC performance summary graph generated by Tuning Fork, including target utilization, heap memory use, and application utilization.
内存管理器依赖作为相邻内存slab的堆，因此当堆需要扩展时无法分配更多本机内存；所有堆内存必须预先保留。
The memory manager relies on the heap being a contiguous slab of memory, so it's impossible to allocate more native memory when the heap needs to expand; all heap memory must be reserved up front.
一旦这些堆被分配，就会创建新的。net对象实例。这个对象将被存储在堆内存断中，此时也将内存提交。
Once these heaps are created and we create a new instance of a.net object this object is stored in these heap segments and memory is committed.
LotusDomino最初将前两个可用的段(0x3和0x4)作为用户堆内存，将最后一个段(0xf)作为共享内存。
Lotus Domino begins using the first two available segments for user heap memory (0x3 and 0x4). Lotus Domino begins using the last segment (0xf) for Shared memory.
对大多数收集器实现而言，分配子系统持有一个自由堆内存池，应用程序通过分配对象使用该池，然后由收集器通过清理来补充该池。
For most collector implementations, the allocation subsystem keeps a pool of free heap memory, consumed by the application through allocating objects and replenished by the collector through sweeping.
目前大多数移动设备的资源都非常宝贵，尤其是堆内存和包容量受到了很大的限制，本文研究了堆内存的管理和资源的减容。
The mobile equipments'resources, especially the heap and package size, are rather limited, so this paper studied the management of heap and reduction of resources'size.
那是用户输入的第一个字节在内存中堆的地址。
That is the address in memory in the heap of the first byte that the user typed in.
当执行数据库监视活动时，将从监视堆分配内存，这些活动包括拍摄快照、打开监视器开关、重置监视器或激活一个事件监视器。
Memory is allocated from the monitor heap when you perform database monitoring activities such as taking a snapshot, turning on a monitor switch, resetting a monitor, or activating an event monitor.
这个值包含调整内存堆大小花费的时间和收集调优决策所需的统计数据花费的时间。
This value includes the time spent resizing the memory heaps and the time spent collecting statistics to make the tuning decision.
用于应用程序管理堆外内存区域和避免垃圾收集(GC)导致的延迟的机制就是一个此类的扩展。
One such extension is a mechanism for applications to manage areas of memory outside of the heap and avoid delays that are caused by garbage collection (GC).
动态段分配让用户堆或共享内存可以使用额外的段。
Dynamic segment allocation allows the additional segments to be used by user heap or Shared memory.
当扩展堆时，分析可用内存趋势会非常困难。
While the heap is expanding, analyzing free memory trends is very problematic.
好像不存在收集参数信息(比如内存堆的使用)的直接的系统调用。
Direct system calls to gather information about parameters (like memory heap usage) don't seem to exist.
堆转储，发现内存泄漏时非常有用。
Heap dumps, which are helpful when hunting for memory leaks.
应用推荐