The high memory strategy activates metering in the event of prolonged high heap memory usage.
HighMemory策略下，当堆内存使用率长时间处于高位时对活动进行计量。
Traditional GC implementations use a stop-the-world (STW) approach to recovering heap memory.
传统GC实现使用stop - the - world (STW)方法来恢复堆内存。
For instance, a health indicator is used to track the consumption of the database heap memory.
例如，健康指示器可以用来跟踪数据库堆内存的消耗量。
If a memory leak is present in your application, the heap memory usage steadily increases over time.
如果您的应用程序出现了内存泄漏，堆内存使用量将随时间稳步增长。
This means that the new area can start at 0x10580000, contiguous with the heap memory that's already committed.
就是说，新的区域可以从0x10580000 开始，与已经提交的堆空间连接在一起。
These two techniques make it possible to avoid heap memory allocation.
这两项技术使人们有可能避免堆内存分配。
The heap memory value in the Profiler will only increase, never decrease.
分析器中的堆内存值仅会增加，而永远不会减少。
After the first collection, free heap memory is primarily the result of objects that were once live but are now dead.
第一次收集后，自由堆内存主要是一些曾经的活对象(现在已死)的结果。
As a result, performance can degrade as the decreased available heap memory leads to more frequent garbage collection.
因此，随着可用堆内存的减少而导致更频繁的垃圾回收，性能可能会降低。
Objects are allocated from the heap; thus the amount of heap memory both used and free are two very important statistics.
对象从堆中分配；因此，使用的和空闲的堆内存数量是两个非常重要的统计信息。
The typical consumer of agent private memory is the sort heap memory that is used by the agent to sort rows during query execution.
代理私有内存的常见消费者是排序堆内存，代理在查询执行期间使用这部分内存来对记录行进行排序。
To cope with the problem of heap memory leak, this paper presents a dynamic memory leak check technology based on red-black tree.
实现时采用红黑树管理所分配的堆内存，理论推导和实验表明其具有较高的效率。
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.
在第2代收集时，用更多CPU周期和堆内存来换取更短的用户界面停顿时间。
Figure 11 shows the GC performance summary graph generated by Tuning Fork, including target utilization, heap memory use, and application utilization.
图11演示了TuningFork所生成的gc性能概要图，包括目标利用率、堆内存使用和应用程序利用率。
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.
LotusDomino最初将前两个可用的段(0x3和0x4)作为用户堆内存，将最后一个段(0xf)作为共享内存。
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.
对大多数收集器实现而言，分配子系统持有一个自由堆内存池，应用程序通过分配对象使用该池，然后由收集器通过清理来补充该池。
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.
对大多数收集器实现而言，分配子系统持有一个自由堆内存池，应用程序通过分配对象使用该池，然后由收集器通过清理来补充该池。
应用推荐