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使用分代垃圾收集算法。
Singleton classes destroyed by garbage collection, then reloaded.
单例对象被垃圾回收机制回收，然后单例类又被重新加载。
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周期。
JDK 1.4.1 also includes numerous options for tuning garbage collection.
JD K1.4.1还包括大量的微调垃圾收集的选项。
Figure 3 charts the garbage collection intervals for each of the four heap sizes.
图3展示了四种堆大小的垃圾收集间隔时间。
No problems were noted, with the exception of very chatty garbage collection.
没有问题被注意到，除了垃圾收集的问题。
Graph showing JIT compilations, class loader information, and garbage collection.
展示JIT编译、类加载器信息和垃圾收集的图形。
The default value of 2 specifies that garbage collection occurs irrespective of the limits.
默认值2指定垃圾收集的发生不考虑限制。
In effect, as the nursery is made larger, the overall time spent in garbage collection drops.
事实上，随着托儿所空间增大，垃圾收集所需的总时间会随之降低。
The garbage collection pause times are the most significant delays any threads encounter.
垃圾收集停顿时间是任何线程遇到的最显著的延迟。
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.
有关微调垃圾收集的更多细节请参阅参考资料中的几篇文章。
Next, understand your application's garbage collection requirements and tune the JVM accordingly.
接下来，了解应用程序的垃圾收集需求并相应地调整J VM。
NILFS2 realized online garbage collection that reclaims disk space with keeping multiple snapshots.
NILFS2实现了在线的垃圾回收，在保持多个快照的同时回收磁盘空间。
A second, less obvious, way is to choose a policy that maximizes the benefits of garbage collection.
第二种不是很明显的方法是选择能够最大化垃圾收集的益处的策略。
This will give you information on the frequency, timing, and duration of garbage collection operations.
这会使您得到垃圾收集操作的频率、定时和持续时间等信息。
Fewer objects created mean less-frequent garbage collection, which has a direct impact on user experience.
越少的对象创建意味着越少的垃圾回收，这会提高你程序的用户体验质量。
This approach is preferred when garbage collection for the servant region JVM is reasonable and acceptable.
当服务区域JVM的垃圾收集合理和可接受时，此方法是首选的方法。
However, too much garbage collection can and will have an adverse effect on your application's performance.
然而，过于频繁的垃圾收集可能、并且将会对您的应用程序的性能产生反作用。
The JVM also requires priorities for internal threads for special purposes such as garbage collection (GC).
JVM还需要对内部线程使用优先级以达到一些特殊目的，比如垃圾收集（GC）。
Garbage collection works in a number of configurable ways through the deferred page space allocation policy.
可以通过延迟的分页空间分配策略以多种可配置的方式执行垃圾收集。
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.
要以最佳方式处理这些不同种类的工作负载，则需要使用不同的垃圾收集策略。
Normally, the file system operates very quickly, but when garbage collection is required, performance slows down.
一般情况下，这种文件系统非常快，但是一旦需要进行垃圾收集，性能就会慢下来。
The downside is that it's log structured, and garbage collection is needed to clean up old data and metadata.
而缺点在于，它是日志结构的，所以需要垃圾收集，以便清理旧的数据和元数据。
During the garbage collection process the garbage collector often moves objects to different locations in the heap.
在垃圾收集过程中，垃圾收集器经常吧对象移动到堆中的另外一个位置。
应用推荐