Garbage collection can have a big effect on application performance.
垃圾收集对应用程序的性能具有很大影响。
The next line indicates the same information, but denotes a full garbage collection.
第二行指示相同的信息，但表示一个完整的垃圾收集。
Verbose garbage collection is not as verbose as the name suggests.
详细垃圾收集并非像其名称暗示的那样详细。
What percentage of the total available CPU time is spent in garbage collection?
总的可用CPU时间用在垃圾收集上的百分比是多少？
Garbage collection (GC) will usually kick in when a memory allocation failure occurs.
当出现内存分配失败的时候，通常将启动垃圾收集(GC)。
Then, examine the garbage collection logs.
然后，研究垃圾收集日志。
The first line in the example above indicates a garbage collection occurred.
上面示例中的第一行指示发生了一次垃圾收集。
While garbage collection must be tolerated, arduously long pause times are another matter entirely.
尽管必须忍受垃圾收集，但是暂停时间太长完全是另一回事。
Contrary to popular belief, garbage collection does not cause the application server to lose requests.
与流行的看法相反，垃圾收集不会导致应用程序服务器丢失请求。
How does garbage collection work?
垃圾收集如何工作？
We also recommend that you enable verbose garbage collection tracing.
我们还建议启用详细的垃圾收集跟踪。
The most straightforward garbage collection strategy is reference counting.
最直观的垃圾收集策略是引用计数。
The JVM is effectively paused during the garbage collection run.
在运行垃圾收集期间，JVM实际上会暂停。
Reference objects introduce some additional costs into the garbage collection process.
引用对象给垃圾收集过程带来了一些附加的成本。
The three most important are garbage collection, managing bad blocks, and wear leveling.
三个最重大的挑战分别是垃圾收集、管理坏块和平均读写。
How does the change impact garbage collection?
更改如何影响垃圾收集？
Using garbage collection to simplify memory management for lists.
使用垃圾收集器来简化列表的内存管理。
To understand this, the first thing you need to check is garbage collection.
要理解这一点，首先需要检查的是垃圾收集。
JVM heap size parameters directly influence garbage collection behavior.
jvm堆大小参数将直接影响垃圾收集行为。
Obviously, a lot of garbage collection can really slow down your application.
显然，大量的垃圾收集可以真正减慢应用程序的运行速度。
Application load, garbage collection concurrency, locality, and allocation efficiencies can all influence application performance.
应用程序负载、垃圾收集并发、位置和分配效率都可能影响应用程序性能。
Either way, your JVM's output will now include the garbage collection information.
无论采用哪种方法，JVM的输出现在都会包含垃圾收集信息。
The graph in Figure 8 shows the garbage collection action for the JSPX-XHTML sample application.
图8 中的图形展示JSPX-XHTML示例应用程序的垃圾收集动作。
It turns out that for most objects, the direct garbage collection cost is — zero.
对于多数对象来说，直接垃圾收集的成本为零。
In certain situations, however, garbage collection performance nosedives for no apparent reason.
但是在某些情况下，垃圾收集的性能会莫名其妙地迅速降低。
OK, so which of these approaches does the JDK take for garbage collection?
那么JDK 使用了哪种方式进行垃圾收集呢？
This is when garbage collection becomes unavoidable.
这时候就不可避免要进行垃圾收集。
This creates the best balance between the rate and length of garbage collection cycles.
这样就能够在垃圾回收周期的频率和长度之间实现最佳的平衡。
This creates the best balance between the rate and length of garbage collection cycles.
这样就能够在垃圾回收周期的频率和长度之间实现最佳的平衡。
应用推荐