最直观的垃圾收集策略是引用计数。
The most straightforward garbage collection strategy is reference counting.
jvm调优的另一个重要方面是垃圾收集策略。
Another important aspect of JVM tuning is the garbage collection policy. The three main GC policies are.
要以最佳方式处理这些不同种类的工作负载，则需要使用不同的垃圾收集策略。
To optimally handle these different sorts of workloads, different garbage collection strategies are required.
根据短寿对象和长寿对象的混合比例，不同垃圾收集策略的性能会有非常大的差别。
The various garbage collection strategies perform very differently depending on the mix of short-lived and long-lived objects.
IBMJ VM支持许多垃圾收集策略，它允许您选择最适合您的应用程序的策略。
The IBM JVM supports several garbage collection policies to enable you to choose the strategy that best fits your application.
在这个案例中，我们用典型的三层客户机-服务器应用程序来研究垃圾收集策略的选择如何影响应用程序性能。
In this case study, we examine how the choice of garbage collection policy affects application performance with a fairly typical three-tiered client-server application.
本系列第2部分将介绍一种基于区域的新的垃圾收集策略balanced，该策略旨在在64位大型多核系统上部署时提高可伸缩性。
Part 2 of this series will introduce a new region-based garbage collection strategy, called balanced, which is designed to improve scalability when deploying on large 64bit multi-core systems.
不同的垃圾收集实现使用不同的策略来识别和收回不可到达的对象，它们与用户程序和调度器以不同的方式互动。
The various garbage collection implementations use different strategies for identification and reclamation of unreachable objects, and they interact differently with the user program and scheduler.
通过匹配工作负载类型及其使用的GC策略并选择适当的堆参数，应该能够减少垃圾收集对应用程序的影响。
By matching the GC policy used to the type of workload and choosing suitable heap parameters, the impact of garbage collection on the application can be reduced.
优化性能的一个明显方法是选择能够最小化垃圾收集停顿时间带来的消极影响的GC策略。
One obvious way to optimize application performance is to choose a GC policy that minimizes any negative impact of garbage collection pauses.
第二种不是很明显的方法是选择能够最大化垃圾收集的益处的策略。
A second, less obvious, way is to choose a policy that maximizes the benefits of garbage collection.
另一方面，当系统超载时，线程需要等待其他线程，就像等待垃圾收集一样，并且两种策略的最大响应时间都会急剧增加。
When the system is overloaded, on the other hand, threads need to wait for other threads as well as for the garbage collector, and the maximum response times increase sharply for both policies.
检查您的JVM所支持的策略，看看使用不同的策略是否会改善吞吐量与垃圾收集引入的暂停之间的平衡关系。
Check your JVM for the policies that it supports to see whether using a different policy can improve the balance between throughput and the pauses that garbage collection introduces.
有几种垃圾收集的基本策略：引用计数、标记-清除、标记-整理 (mark-compact)和复制。
There are several basic strategies for garbage collection: reference counting, mark-sweep, mark-compact, and copying.
您可以执行的最简单的调整就是指定一个策略并告诉垃圾收集器是吞吐量重要还是暂停时间最重要。
The simplest tuning you can do is to specify a policy and tell the garbage collector whether throughput or pause times are most important.
垃圾收集器然后根据当前收集所回收的内存总量和其他策略考虑因素，判断软引用此时是否需要被清除。
The garbage collector then assesses whether soft references need to be cleared at this time, based on the amount of memory reclaimed by the current collection and other policy considerations.
可以通过延迟的分页空间分配策略以多种可配置的方式执行垃圾收集。
Garbage collection works in a number of configurable ways through the deferred page space allocation policy.
分代收集器对不同的代可以自由使用不同的收集策略，对各代分别进行垃圾收集。
A generational collector is free to use a different collection strategy for different generations and perform garbage collection on the generations separately.
VerboseGC日志能够洞察垃圾收集器的操作，并为策略和参数选择提供提示。
Verbose GC logs give insight into the operation of the garbage collector and can give hints about policy and parameter choices.
程序刚开始运行，垃圾收集器分配为每一代分配了一定的内存，这些内存的初始大小由。netframework的策略决定。
When the program initializes, garbage collector allocates memory for generations. The initial size of memory blocks are determined according to the strategies of the. Net framework.
程序刚开始运行，垃圾收集器分配为每一代分配了一定的内存，这些内存的初始大小由。netframework的策略决定。
When the program initializes, garbage collector allocates memory for generations. The initial size of memory blocks are determined according to the strategies of the. Net framework.
应用推荐