Next it shows overall garbage collection stats.
接着，它展示了总体的垃圾收集统计信息。
Problems related to garbage collection and serialization
与垃圾收集和序列化有关的问题
SUN's JVM 1.3.1 USES a generational garbage collection algorithm.
SUN的JVM1.3.1使用分代垃圾收集算法。
The LPGC provides garbage collection in parallel to the JVM's work.
LPGC提供与JVM的工作并行的垃圾收集功能。
This will increase CPU cycles with garbage collection of UI objects.
这会随着UI对象的垃圾收集而增加CPU周期。
Figure 3 charts the garbage collection intervals for each of the four heap sizes.
图3展示了四种堆大小的垃圾收集间隔时间。
Graph showing JIT compilations, class loader information, and garbage collection.
展示JIT编译、类加载器信息和垃圾收集的图形。
The pause time is the amount of time that a garbage collection cycle took to complete.
暂停时间是垃圾收集周期完成所需的时间。
An exception is thrown on the garbage collection thread when you use SQL providers.
使用SQLprovider时，垃圾回收线程抛出异常。
The garbage collection pause times are the most significant delays any threads encounter.
垃圾收集停顿时间是任何线程遇到的最显著的延迟。
Here is an example that shows the effect heavy garbage collection has in a real situation.
这里提供了一个示例，该示例说明了在真实的情况中，繁重的垃圾收集对系统产生的影响。
The default value of 2 specifies that garbage collection occurs irrespective of the limits.
默认值2指定垃圾收集的发生不考虑限制。
It also provides a toolbar button to force the JVM to perform garbage collection when desired.
它还提供了一个工具栏按钮，必要时可以强制JVM执行垃圾收集。
See Resources for a number of articles offering more detailed garbage collection tuning advice.
有关微调垃圾收集的更多细节请参阅参考资料中的几篇文章。
Total time spent in garbage collection should be no more than 15% of the duration of the test.
垃圾回收占用的总时间应该不超过测试持续时间的15%。
It shows the sequence of garbage collection cycles that occurred throughout the life of that JVM.
它显示了JVM生存期间，各个垃圾回收周期的顺序。
The JVM may continue growing the heap rather than wait for a garbage collection cycle to complete.
JVM可能继续增大堆，而不等待一个垃圾收集周期的完成。
The first version of NILFS (version 1) appeared in 2005 but lacked any form of garbage collection.
第一版的NILFS（version1）出现于 2005 年，这个版本没有任何形式的垃圾收集。
NILFS2 realized online garbage collection that reclaims disk space with keeping multiple snapshots.
NILFS2实现了在线的垃圾回收，在保持多个快照的同时回收磁盘空间。
Two further parameters, rpgclean and rpgcontrol, specify how the garbage collection should operate.
另外两个参数rpgclean和rpgcontrol指定如何执行垃圾收集。
A second, less obvious, way is to choose a policy that maximizes the benefits of garbage collection.
第二种不是很明显的方法是选择能够最大化垃圾收集的益处的策略。
The result is that garbage collection will need to be performed in order to reclaim space in the heap.
结果是需要执行垃圾收集以便回收堆中的空间。
This will give you information on the frequency, timing, and duration of garbage collection operations.
这会使您得到垃圾收集操作的频率、定时和持续时间等信息。
When evaluating a garbage collection algorithm, we might consider any or all of the following criteria.
在对垃圾收集算法进行评价时，我们可能要考虑以下所有标准。
Using the default GC policy, the IBM JVM will consume the entire heap before invoking garbage collection.
在使用默认的GC策略的情况下，IBMJVM 在耗尽所有堆之后才调用垃圾回收。
This approach is preferred when garbage collection for the servant region JVM is reasonable and acceptable.
当服务区域JVM的垃圾收集合理和可接受时，此方法是首选的方法。
The JVM also requires priorities for internal threads for special purposes such as garbage collection (GC).
JVM还需要对内部线程使用优先级以达到一些特殊目的，比如垃圾收集（GC）。
By arranging for most objects to survive less than one collection, garbage collection can be very efficient.
通过安排大多数对象的存活期不超过一个收集周期，垃圾收集可以变得非常有效。
Enable verbose garbage collection logging in your JVM, which will start logging garbage collection activity.
在JVM中启用详细垃圾收集日志记录，这会开始记录垃圾收集活动。
To optimally handle these different sorts of workloads, different garbage collection strategies are required.
要以最佳方式处理这些不同种类的工作负载，则需要使用不同的垃圾收集策略。
应用推荐